Linux: Update kernel to 6.12.18

[sairon]

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

Summary by CodeRabbit

• Documentation
  • Updated hardware board version details to 6.12.18 in the documentation.
• Chores
  • Upgraded the Linux kernel version to 6.12.18 across various configuration setups, ensuring improved performance and security.

This release harmonizes versioning across supported hardware platforms and system configurations for a more consistent experience.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates kernel version information across documentation and build configuration files. In the documentation file, multiple hardware board entries have their version numbers changed from 6.12.17 to 6.12.18. Similarly, all build configuration files for various boards in the Buildroot external repository have their custom Linux kernel version updated from 6.12.17 to 6.12.18.

Changes

File(s)	Change Summary
Documentation/kernel.md	Updated version numbers for several hardware boards (e.g., Open Virtual Appliance, Home Assistant Green, Tinker Board, ODROID variants, Generic aarch64/x86-64, Khadas VIM3) from 6.12.17 to 6.12.18.
buildroot-external/configs/*.defconfig	Updated the kernel version configuration (BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE) from "6.12.17" to "6.12.18" across all defconfig files.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4a1d2b7 and 95e7021.

📒 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 doc...

*/**(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'

• Documentation/kernel.md

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

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

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

• Documentation/kernel.md

`*/**(html|markdown|md)`: - Be brief in your replies and don...

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

• Documentation/kernel.md

`*/**(html|markdown|md)`: - Use sentence-style capitalizatio...

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

• Documentation/kernel.md

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

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

• Documentation/kernel.md

`*/**(html|markdown|md)`: Avoid flagging inline HTML for emb...

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

• Documentation/kernel.md

🔇 Additional comments (14)

buildroot-external/configs/odroid_m1s_defconfig (1)

19-19: Kernel version update looks good.

The Linux kernel version has been updated from 6.12.17 to 6.12.18, which aligns with the PR objective of updating the kernel.

buildroot-external/configs/odroid_c2_defconfig (1)

19-19: Kernel version update looks good.

The Linux kernel version has been updated from 6.12.17 to 6.12.18, which aligns with the PR objective of updating the kernel.

buildroot-external/configs/khadas_vim3_defconfig (1)

19-19: Kernel version update looks good.

The Linux kernel version has been updated from 6.12.17 to 6.12.18, which aligns with the PR objective of updating the kernel.

buildroot-external/configs/generic_x86_64_defconfig (1)

19-19: Kernel version update looks good.

The Linux kernel version has been updated from 6.12.17 to 6.12.18, which aligns with the PR objective of updating the kernel.

buildroot-external/configs/odroid_c4_defconfig (1)

19-19: Kernel version update looks good.

Updated Linux kernel version from 6.12.17 to 6.12.18 for the ODROID-C4 board configuration. This change aligns with the PR objective.

buildroot-external/configs/ova_defconfig (1)

19-19: Kernel version update looks good.

Updated Linux kernel version from 6.12.17 to 6.12.18 for the Open Virtual Appliance (OVA) configuration. This change is consistent with the updates in other configuration files.

buildroot-external/configs/odroid_m1_defconfig (1)

19-19: Kernel version update looks good.

Updated Linux kernel version from 6.12.17 to 6.12.18 for the ODROID-M1 board configuration. This change maintains version consistency across the platform.

buildroot-external/configs/green_defconfig (1)

19-19: Kernel version update looks good.

Updated Linux kernel version from 6.12.17 to 6.12.18 for the Green board configuration. This change properly completes the kernel version update across all configurations.

buildroot-external/configs/odroid_n2_defconfig (1)

19-19: Verified kernel version update

The update from Linux kernel version 6.12.17 to 6.12.18 looks good. This is consistent with the PR objective to update the kernel version.

buildroot-external/configs/generic_aarch64_defconfig (1)

19-19: Verified kernel version update

The update from Linux kernel version 6.12.17 to 6.12.18 is correct and aligns with the PR's objective.

buildroot-external/configs/odroid_xu4_defconfig (1)

20-20: Verified kernel version update

The update from Linux kernel version 6.12.17 to 6.12.18 is consistent with the other configuration files and matches the PR's purpose.

buildroot-external/configs/tinker_defconfig (1)

21-21: Verified kernel version update

The update from Linux kernel version 6.12.17 to 6.12.18 is correctly implemented, consistent with the other configuration files, and fulfills the PR's objective.

Documentation/kernel.md (2)

6-6: Verify kernel version update for Open Virtual Appliance.
The version for Open Virtual Appliance is updated to 6.12.18 in this row, which aligns with the PR objective to update the kernel version.

---

14-24: Confirm kernel version updates for multiple boards.
The kernel versions for Home Assistant Green, Tinker Board, ODROID-C2, ODROID-C4, ODROID-M1, ODROID-M1S, ODROID-N2, ODROID-XU4, Generic aarch64, Generic x86-64, and Khadas VIM3 have been updated to 6.12.18. These changes are consistent with the PR objectives to update the kernel version, and the entries reflect the intended version upgrade.

---

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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.