From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Luis Chamberlain <mcgrof@kernel•org>, Kees Cook <kees@kernel•org>,
Joel Granados <joel.granados@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 sysctl tree
Date: Wed, 30 Jul 2025 17:16:26 +1000 [thread overview]
Message-ID: <20250730171626.5ea7e0df@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 303 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
(looks like all the commits in the sysctl tree)
I guess it was rebased before the pull request was sent to Linus.
Please clean up the sysctl tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-07-30 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 7:16 Stephen Rothwell [this message]
2025-08-04 7:38 ` linux-next: duplicate patches in the sysctl tree Joel Granados
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=20250730171626.5ea7e0df@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=joel.granados@kernel$(echo .)org \
--cc=kees@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mcgrof@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