Linux: Update kernel to 6.12.35

[sairon]

• https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.35

Summary by CodeRabbit

• Chores
  • Updated the Linux kernel version from 6.12.34 to 6.12.35 for multiple supported boards and platforms, including Open Virtual Appliance, Home Assistant Green, Tinker Board, ODROID models, Generic aarch64, Generic x86-64, and Khadas VIM3. No other changes were made.

[coderabbitai]

📝 Walkthrough

Walkthrough

The kernel version for multiple board configurations and documentation references was updated from 6.12.34 to 6.12.35. This affects various Buildroot configuration files and the documentation, with no other changes to configuration options, parameters, or content.

Changes

Files/Groups	Change Summary
Documentation/kernel.md	Updated kernel version numbers for several boards.
buildroot-external/configs/generic_aarch64_defconfig	Kernel version updated from 6.12.34 to 6.12.35.
buildroot-external/configs/generic_x86_64_defconfig	Kernel version updated from 6.12.34 to 6.12.35.
buildroot-external/configs/green_defconfig	Kernel version updated from 6.12.34 to 6.12.35.
buildroot-external/configs/khadas_vim3_defconfig	Kernel version updated from 6.12.34 to 6.12.35.
buildroot-external/configs/odroid_*_defconfig	Kernel version updated from 6.12.34 to 6.12.35 for all Odroid boards (C2, C4, M1, M1S, N2, XU4).
buildroot-external/configs/ova_defconfig	Kernel version updated from 6.12.34 to 6.12.35.
buildroot-external/configs/tinker_defconfig	Kernel version updated from 6.12.34 to 6.12.35.

Sequence Diagram(s)

No sequence diagrams are generated as the changes are limited to version updates and do not affect control flow or introduce new features.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between da9c531 and ab2e526.

📒 Files selected for processing (13)

• Documentation/kernel.md (1 hunks)
• buildroot-external/configs/generic_aarch64_defconfig (1 hunks)
• buildroot-external/configs/generic_x86_64_defconfig (1 hunks)
• buildroot-external/configs/green_defconfig (1 hunks)
• buildroot-external/configs/khadas_vim3_defconfig (1 hunks)
• buildroot-external/configs/odroid_c2_defconfig (1 hunks)
• buildroot-external/configs/odroid_c4_defconfig (1 hunks)
• buildroot-external/configs/odroid_m1_defconfig (1 hunks)
• buildroot-external/configs/odroid_m1s_defconfig (1 hunks)
• buildroot-external/configs/odroid_n2_defconfig (1 hunks)
• buildroot-external/configs/odroid_xu4_defconfig (1 hunks)
• buildroot-external/configs/ova_defconfig (1 hunks)
• buildroot-external/configs/tinker_defconfig (1 hunks)

🧰 Additional context used

📓 Path-based instructions (6)

`*/**(html|markdown|md)`: - For instructional content in documentation, use a di...

*/**(html|markdown|md): - For instructional content in documentation, use a direct and authoritative tone. Avoid expressions of politeness such as 'may' or 'please', and ensure the goal of the instruction is fronted.

• Apply the Microsoft Style Guide to ensure documentation maintains clarity and conciseness.
• In step-by-step instructions, front the location phrase in the instructional sentence.
• In step-by-step instructions, front the 'goal' in the instructional sentence.
• In step-by-step instructions, if in doubt what to front, front the 'goal' before the location phrase in the instructional sentence.
• do not hyphenate terms like 'top-right' or 'bottom-left' with 'corner'

⚙️ Source: CodeRabbit Configuration File

List of files the instruction was applied to:

• Documentation/kernel.md

`*/**(html|markdown|md)`: - Use bold to mark UI strings. - If "" are used to mark UI strings, replace them by bold.

*/**(html|markdown|md): - Use bold to mark UI strings.

• If "" are used to mark UI strings, replace them by bold.

⚙️ Source: CodeRabbit Configuration File

List of files the instruction was applied to:

• Documentation/kernel.md

`*/**(html|markdown|md)`: - Be brief in your replies and don't add fluff like "thank you for..." and "Please let me know if"

*/**(html|markdown|md): - Be brief in your replies and don't add fluff like "thank you for..." and "Please let me know if"

⚙️ Source: CodeRabbit Configuration File

List of files the instruction was applied to:

• Documentation/kernel.md

`*/**(html|markdown|md)`: - Use sentence-style capitalization also in headings.

*/**(html|markdown|md): - Use sentence-style capitalization also in headings.

⚙️ Source: CodeRabbit Configuration File

List of files the instruction was applied to:

• Documentation/kernel.md

`*/**(html|markdown|md)`: do not comment on HTML used for icons

*/**(html|markdown|md): do not comment on HTML used for icons

⚙️ Source: CodeRabbit Configuration File

List of files the instruction was applied to:

• Documentation/kernel.md

`*/**(html|markdown|md)`: Avoid flagging inline HTML for embedding videos in future reviews for this repository.

*/**(html|markdown|md): Avoid flagging inline HTML for embedding videos in future reviews for this repository.

⚙️ Source: CodeRabbit Configuration File

List of files the instruction was applied to:

• Documentation/kernel.md

🔇 Additional comments (13)

buildroot-external/configs/odroid_c2_defconfig (1)

20-20: Kernel bump to 6.12.35 looks correct

No other parameters depend on the micro-version, so this single-line change is sufficient here.

buildroot-external/configs/odroid_m1s_defconfig (1)

20-20: Kernel version updated consistently

Nothing else in the defconfig couples to the exact sub-version; change is good as-is.

buildroot-external/configs/odroid_n2_defconfig (1)

20-20: LGTM – version string only

The bump matches the rest of the PR and should not affect build output beyond pulling the new tarball.

buildroot-external/configs/odroid_m1_defconfig (1)

20-20: Straightforward kernel bump

Verified that no board-specific patches in board/hardkernel/odroid-m1/ are hard-coded to 6.12.34, so the change is safe.

buildroot-external/configs/generic_aarch64_defconfig (1)

20-20: No stale references to the previous kernel version
Ran rg -n "6\.12\.34" across the repository and confirmed zero matches, so the bump to 6.12.35 is complete.

buildroot-external/configs/ova_defconfig (1)

20-20: Kernel bump looks correct; please manually verify out-of-tree patches

The version string has been updated to 6.12.35, which matches the 6.12.y directory. To ensure no patches in board/pc/ova/patches or kernel/v6.12.y fail to apply, please run the following in your Buildroot checkout:

cd buildroot
make O=/tmp/ova_build \
     BR2_EXTERNAL=$(pwd)/../buildroot-external \
     defconfig BR2_DEFCONFIG=../buildroot-external/configs/ova_defconfig

make O=/tmp/ova_build linux-patches

# (optional) to reconfigure the Linux kernel
make O=/tmp/ova_build linux-reconfigure

If any patch fails, update or remove it as needed before merging.

buildroot-external/configs/generic_x86_64_defconfig (1)

20-20: Version updated consistently to 6.12.35

No additional adjustments are necessary; fragment directory already tracks v6.12.y.
Same verification advice as for OVA applies here.

buildroot-external/configs/tinker_defconfig (1)

22-22: Kernel version synchronized – OK

The bump is in line with the other boards. Ensure the RK3288 DTS and any vendor patches still compile, but the defconfig itself needs no further edits.

buildroot-external/configs/odroid_xu4_defconfig (1)

21-21: Kernel bump for XU4 acknowledged

Looks good. Given Exynos-specific patches, a quick linux-patches dry-run is advised.

buildroot-external/configs/green_defconfig (1)

20-20: Green board follows the fleet to 6.12.35

All good. Rockchip 3566 patches should still apply cleanly; no config tweak required.

buildroot-external/configs/odroid_c4_defconfig (1)

20-20: Consistent kernel bump – no objections

The patch-level upgrade to 6.12.35 is isolated and all other 6.12-series references (header selection, fragment path v6.12.y, external patches) stay coherent.
No further changes required from my side.

buildroot-external/configs/khadas_vim3_defconfig (1)

20-20: Kernel version sync acknowledged

BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE now points to 6.12.35, matching the rest of the bump series. Everything else (headers, fragments, patch dir) still targets the generic v6.12.y stream, so this is internally consistent.

Documentation/kernel.md (1)

6-24: Documentation correctly mirrors defconfig bumps

The table now lists 6.12.35 for every board that had its defconfig updated, maintaining consistency between docs and build specs.
No wording-style or formatting issues found.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.