mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>,
	Nicolas Schier <nsc@kernel.org>,
	KBuild Mailing List <linux-kbuild@vger.kernel.org>
Cc: Gary Guo <gary@garyguo.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Miguel Ojeda <ojeda@kernel.org>
Subject: linux-next: manual merge of the kbuild tree with the rust tree
Date: Mon, 5 Oct 2026 12:31:22 +0200	[thread overview]
Message-ID: <asN8ejNILKW2YWep@sirena.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

Hi all,

Today's linux-next merge of the kbuild tree got a conflict in:

  scripts/remove-stale-files

between commit:

  a41ec2936d2fe ("rust: doctest: generate Rust kunit test suites")

from the rust tree and commit:

  33bef82263082 ("kbuild: Move gen_init_cpio and gen_initramfs.sh to scripts/")

from the kbuild tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

diff --cc scripts/remove-stale-files
index f1f776caae00a,e46337e4bfb8f..0000000000000
--- a/scripts/remove-stale-files
+++ b/scripts/remove-stale-files
@@@ -27,4 -27,4 +27,6 @@@ rm -f *.spe
  
  rm -f lib/test_fortify.log
  
 +rm -f rust/doctests_kernel_generated_kunit.c
++
+ rm -f usr/gen_init_cpio

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2026-10-05 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 10:31 Mark Brown [this message]
2026-10-05 11:05 ` Nathan Chancellor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=asN8ejNILKW2YWep@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=gary@garyguo.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=nsc@kernel.org \
    --cc=ojeda@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®