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: Fri, 22 Dec 2023 10:48:10 +1100 [thread overview]
Message-ID: <20231222104810.32247f14@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
Hi all,
The following commits are also in the kbuild-fixes tree as different
commits (but the same patches):
44028378399f ("gen_compile_commands.py: fix path resolve with symlinks in it")
888a50f6f93a ("MAINTAINERS: Add scripts/clang-tools to Kbuild section")
These are commits
7cdb9dd97e6e ("gen_compile_commands.py: fix path resolve with symlinks in it")
e231092d19b8 ("MAINTAINERS: Add scripts/clang-tools to Kbuild section")
in the kbuild-fixes tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-12-21 23:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 23:48 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-13 0:39 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=20231222104810.32247f14@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