From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Masahiro Yamada <masahiroy@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the kbuild tree
Date: Tue, 13 May 2025 10:39:07 +1000 [thread overview]
Message-ID: <20250513103907.3aad5afd@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
Hi all,
The following commits are also in the kbuild-current tree as different
commits (but the same patches):
188d818d66b7 ("init: remove unused CONFIG_CC_CAN_LINK_STATIC")
cece6e78ad37 ("um: let 'make clean' properly clean underlying SUBARCH as well")
8d5f08b84e6e ("kbuild: Disable -Wdefault-const-init-unsafe")
e08558fae8dd ("kbuild: rpm-pkg: Add (elfutils-devel or libdw-devel) to BuildRequires")
3a0a25a4cf18 ("kbuild: deb-pkg: Add libdw-dev:native to Build-Depends-Arch")
20511f5e38a5 ("usr/include: openrisc: don't HDRTEST bpf_perf_event.h")
32562a619812 ("kbuild: Require pahole <v1.28 or >v1.29 with GENDWARFKSYMS on X86")
These are commits
d1b99cdf22e0 ("init: remove unused CONFIG_CC_CAN_LINK_STATIC")
ab09da75700e ("um: let 'make clean' properly clean underlying SUBARCH as well")
d0afcfeb9e38 ("kbuild: Disable -Wdefault-const-init-unsafe")
5bd6bdd0f76e ("kbuild: rpm-pkg: Add (elfutils-devel or libdw-devel) to BuildRequires")
657f96cb7c06 ("kbuild: deb-pkg: Add libdw-dev:native to Build-Depends-Arch")
56045757accf ("usr/include: openrisc: don't HDRTEST bpf_perf_event.h")
9520a2b3f0b5 ("kbuild: Require pahole <v1.28 or >v1.29 with GENDWARFKSYMS on X86")
in the kbuild-current tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-05-13 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 0:39 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-21 23:48 linux-next: duplicate patches in the kbuild tree Stephen Rothwell
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=20250513103907.3aad5afd@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=masahiroy@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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