Skip to content

fix(spi): Add missing initializer for ss_invert#11320

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
me-no-dev merged 2 commits into from
Apr 29, 2025
Merged

fix(spi): Add missing initializer for ss_invert #11320

me-no-dev merged 2 commits into from
Apr 29, 2025

Conversation

@lucasssvaz
Copy link
Member

@lucasssvazlucasssvaz commented Apr 28, 2025

Description of Change

Add missing value to spi struct for ss_invert.

Related links

Fixes#11297

@lucasssvazlucasssvaz self-assigned this Apr 28, 2025
@lucasssvazlucasssvaz added the Status: Review needed Issue or PR is awaiting review label Apr 28, 2025
@github-actions
Copy link
Contributor

github-actionsbot commented Apr 28, 2025•
edited
Loading

Messages
📖🎉 Good Job! All checks are passing!

👋 Hello lucasssvaz, we appreciate your contribution to this project!

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.
🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.
Click to see more instructions ...


This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against b048813

@github-actions
Copy link
Contributor

github-actionsbot commented Apr 28, 2025•
edited
Loading

Test Results

76 files 76 suites 12m 42s ⏱️
38 tests 38 ✅ 0 💤 0 ❌
241 runs 241 ✅ 0 💤 0 ❌

Results for commit b048813.

♻️ This comment has been updated with latest results.

@me-no-devme-no-dev added Status: Pending Merge Pull Request is ready to be merged and removed Status: Review needed Issue or PR is awaiting review labels Apr 29, 2025
@me-no-devme-no-dev merged commit 543fad2 into espressif:masterApr 29, 2025
57 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@me-no-devme-no-devme-no-dev approved these changes

@P-R-O-C-H-YP-R-O-C-H-YP-R-O-C-H-Y approved these changes

Assignees

@lucasssvazlucasssvaz

Labels

Status: Pending MergePull Request is ready to be merged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@lucasssvaz@me-no-dev@P-R-O-C-H-Y