All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"Borislav Petkov (AMD)" <bp@alien8.de>
Subject: Re: linux-next: duplicate patches in the tip tree
Date: Mon, 4 Mar 2024 10:21:12 +0100	[thread overview]
Message-ID: <ZeWSiIKiL+8H2LqO@gmail.com> (raw)
In-Reply-To: <20240304092140.0adb0f26@canb.auug.org.au>


* Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
> 
>   9e1daa3bfccc ("x86/e820: Don't reserve SETUP_RNG_SEED in e820")
> 
> This is commit
> 
>   7fd817c90650 ("x86/e820: Don't reserve SETUP_RNG_SEED in e820")
> 
> in Linus' tree.

This was only temporary, should be resolved in the next -next integration.

Thanks,

	Ingo

  reply	other threads:[~2024-03-04  9:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-03 22:21 linux-next: duplicate patches in the tip tree Stephen Rothwell
2024-03-04  9:21 ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-18 21:02 Stephen Rothwell
2024-12-09  2:29 Stephen Rothwell
2024-12-09 11:08 ` Peter Zijlstra
2024-12-09 19:45   ` Andrew Morton
2024-12-09 20:21     ` Suren Baghdasaryan
2024-12-09 22:53       ` Thomas Gleixner
2025-03-11  4:08 Stephen Rothwell
2025-03-11  9:02 ` Andrew Morton
2025-03-11 11:43   ` Stephen Rothwell
2025-03-11 12:56     ` Thomas Gleixner
2025-03-25 21:47 ` Stephen Rothwell
2025-03-20  9:46 Stephen Rothwell
2025-03-20 11:13 ` Mark Brown

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=ZeWSiIKiL+8H2LqO@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.