linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paul E. McKenney" <paulmck@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patch in the rcu tree
Date: Mon, 16 Jan 2023 12:38:21 +1100	[thread overview]
Message-ID: <20230116123821.41d336ea@canb.auug.org.au> (raw)

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

Hi all,

The following commit is also in the tip tree as a different commit
(but the same patch):

  836dc5db1d87 ("context_tracking: Use arch_atomic_*() in __ct_user_enter and __ct_user_exit")

It is commit

  0e26e1de0032 ("context_tracking: Fix noinstr vs KASAN")

in the tip tree.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2023-01-16  1:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16  1:38 Stephen Rothwell [this message]
2023-01-16  4:44 ` linux-next: duplicate patch in the rcu tree Paul E. McKenney
  -- strict thread matches above, loose matches on Subject: below --
2025-06-22 21:52 Stephen Rothwell
2024-08-12  2:51 Stephen Rothwell
2024-02-28  1:06 Stephen Rothwell
2024-02-28  1:17 ` Thomas Gleixner
2024-02-28  1:26   ` Paul E. McKenney
2024-02-28  1:20 ` Paul E. McKenney
2023-11-01  1:01 Stephen Rothwell
2023-11-01 19:17 ` Paul E. McKenney
2023-10-13  4:37 Stephen Rothwell
2023-10-13 13:32 ` Paul E. McKenney
2023-07-14  4:43 Stephen Rothwell
2023-07-14  4:50 ` Paul E. McKenney
2023-07-14  6:04   ` Alexei Starovoitov
2023-07-14 15:03     ` Paul E. McKenney
2023-05-10 23:00 Stephen Rothwell
2023-05-11 16:52 ` Paul E. McKenney
2023-05-15 19:28   ` Shuah Khan
2023-05-16 12:19     ` Paul E. McKenney
2023-05-17 16:12       ` Shuah Khan
2023-05-17 17:07         ` Paul E. McKenney
2023-03-23  3:47 Stephen Rothwell
2023-03-23  3:44 Stephen Rothwell
2023-03-23  5:11 ` Paul E. McKenney
2023-03-23 19:41   ` Andrew Morton
2023-03-23 21:03     ` Paul E. McKenney
2023-01-08 23:11 Stephen Rothwell
2023-01-09  4:36 ` Paul E. McKenney
2023-01-16  1:31 ` Stephen Rothwell
2023-01-16  4:41   ` 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=20230116123821.41d336ea@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).