[WIP] [Deepin-Kernel-SIG] [linux 6.6-y] [RFC] deepin: extra ci: add i386_defconfig

[Avenger-285714]

1. It seems our peers also check for build success under this configuration.

2. At this moment, the code in the deepin linux-6.6.y branch indeed fails to build under that branch.

Summary by Sourcery

CI:

• Extend kernel extra CI workflow to build the i386_defconfig configuration with both GCC and Clang toolchains.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR extends the extra kernel CI workflow to build the deepin 6.6.y kernel with the i386_defconfig using both GCC and Clang, mirroring existing x86_64_defconfig coverage and exposing current build failures under this config.

Flow diagram for new i386_defconfig build steps in CI

flowchart TD
  A["Start build_kernel_extra job"] --> B["Configure git user"]
  B --> C["Compile kernel i386_defconfig using GCC\nmake i386_defconfig && make -j$(nproc)"]
  C --> D["Compile kernel i386_defconfig using Clang\nmake LLVM=-18 i386_defconfig && make LLVM=-18 -j$(nproc)"]
  D --> E["Compile kernel x86_64_defconfig using GCC"]
  E --> F["End job"]

Loading

File-Level Changes

Change	Details	Files
Add i386_defconfig build and Clang build steps to the extra kernel GitHub Actions workflow.	Introduce a GCC-based i386_defconfig compile step using make i386_defconfig followed by a parallel make build. Introduce a Clang-based i386_defconfig compile step using LLVM=-18 with corresponding make i386_defconfig and parallel build commands. Place the new i386_defconfig jobs alongside the existing x86_64_defconfig build steps in the workflow to ensure both architectures are validated in CI.	.github/workflows/build-kernel-extra.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from avenger-285714. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• deepin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Copilot]

Pull request overview

Adds extra CI coverage to validate that the Deepin 6.6-y kernel tree builds under i386_defconfig, aligning with peer CI expectations and helping surface existing 32-bit build regressions earlier.

Changes:

• Add a GCC build step for i386_defconfig in the “build kernel extra” workflow.
• Add a Clang build step for i386_defconfig in the same workflow.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This builds i386 and then later x86_64 (and other ARCH values) in the same source/output tree. Kbuild is not reliable when reusing the same output directory across different defconfigs/bitness/architectures; stale objects can lead to flaky failures or false passes. Use per-config out-of-tree build dirs (e.g., via O=/KBUILD_OUTPUT) or run a clean step (e.g., make mrproper) between architecture/bitness switches.

[Copilot]

The clang i386 build reuses the artifacts from the preceding GCC i386 build in the same directory. Even if many objects rebuild, this can still mask clang-only build issues or cause confusing incremental-build behavior. Consider using a separate O= output dir for the clang pass (or cleaning before the clang build) so it is a true from-scratch clang build for this config.