-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Allwinner kernel: bump current to 6.12.35 and edge to 6.15.4 #8337
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
## Walkthrough
The kernel branch tags in the configuration files for sunxi and sunxi64 devices have been updated. The "current" branch kernel tag was changed from "tag:v6.12.30" to "tag:v6.12.35", and the "edge" branch kernel tag was updated from "tag:v6.15" to "tag:v6.15.4". No other variables or exported/public entity declarations were altered.
## Possibly related PRs
- armbian/build#8100: Both PRs update the kernel branch tags in the same configuration files (sunxi64_common.inc and sunxi_common.inc) for the Allwinner platform, with the main PR advancing the tags further than the retrieved PR.
- armbian/build#8233: The main PR updates the kernel tags from v6.12.30 to v6.12.35 and from v6.15 to v6.15.4, directly continuing the version bump initiated in the retrieved PR which updated the kernel tag to v6.12.30.
- armbian/build#8270: Both PRs update the kernel branch tags for the "current" and "edge" branches in the same sunxi_common.inc and sunxi64_common.inc files, with the main PR advancing the versions beyond those set in the retrieved PR, indicating a direct continuation of the kernel version bumping changes.
## Suggested reviewers
- TheSnowfield 📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
⏰ Context from checks skipped due to timeout of 90000ms (2)
✨ Finishing Touches🧪 Generate Unit Tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Description
How Has This Been Tested?
Checklist: