-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
nanopi-r76s: move patch to board specific folder #9062
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.
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
Conversation
avoid cross-contamination from other boards/families that will use this uboot version in future
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
✅ This PR has been reviewed and approved — all set for merge! |
|
Thanks, I noticed this the other day as well. Btw, since all 3 files are null-patches, they could be extracted from a .patch and be put bare in the |
|
(I expect the r76s to land upstream soon enough, so the whole thing might go away soon. I'd just rather keep v2026.01 null-patch-free if possible) |
|
Perhaps @SuperKali wants to take care of that? |
|
Might wanna hold off a bit, as torvalds/linux@7fee888 just landed in 6.19-rc1 -- might take a while until u-boot rebases dts/upstream onto it |
Description
avoid cross-contamination from other boards/families that will use this uboot version in future
Checklist:
Please delete options that are not relevant.