public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Paul E. McKenney" <paulmck@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 rcu tree
Date: Thu, 11 Apr 2024 16:46:55 +1000	[thread overview]
Message-ID: <20240411164655.781a57d3@canb.auug.org.au> (raw)

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

Hi all,

The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):

  56544e22cc3a ("fs/proc: remove redundant comments from /proc/bootconfig")
  e6f3a323fcfa ("fs/proc: Skip bootloader comment if no embedded kernel paramete

These are commits

  fbbdc255fbee ("fs/proc: remove redundant comments from /proc/bootconfig")
  c722cea20878 ("fs/proc: Skip bootloader comment if no embedded kernel parameters")

in Linus' tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-04-11  6:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  6:46 Stephen Rothwell [this message]
2024-04-12  4:20 ` linux-next: duplicate patches in the rcu tree Paul E. McKenney
  -- strict thread matches above, loose matches on Subject: below --
2023-09-27  1:53 Stephen Rothwell
2023-10-02 15:41 ` Steven Rostedt
2023-10-05 17:19   ` Paul E. McKenney
2023-01-24  1:01 Stephen Rothwell
2023-01-24  4:48 ` Paul E. McKenney
2023-01-06  0:56 Stephen Rothwell
2023-01-06  1:17 ` Paul E. McKenney

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=20240411164655.781a57d3@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=paulmck@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