All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the driver-core.current tree
Date: Wed, 16 Apr 2025 07:49:58 +0200	[thread overview]
Message-ID: <2025041646-resubmit-erasable-4386@gregkh> (raw)
In-Reply-To: <20250416094455.55506561@canb.auug.org.au>

On Wed, Apr 16, 2025 at 09:44:55AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the mm-hotfixes tree as a different commit
> (but the same patch):
> 
>   b9792abb76ae ("drivers/base/memory: Avoid overhead from for_each_present_section_nr()")
> 
> This is commit
> 
>   ab81406e527d ("drivers/base/memory: avoid overhead from for_each_present_section_nr()")
> 
> in the mm-hotfixes-unstable branch of the mm-hotfixes tree.

Looks like Andrew dropped this from his tree now, thanks!

greg k-h

  reply	other threads:[~2025-04-16  5:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 23:44 linux-next: duplicate patch in the driver-core.current tree Stephen Rothwell
2025-04-16  5:49 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-07 20:02 Stephen Rothwell
2025-01-08  8:15 ` Greg KH
2024-04-11 22:43 Stephen Rothwell
2024-04-11 22:43 ` Stephen Rothwell
2024-04-12  4:36 ` Michael Ellerman
2024-04-12  4:36   ` Michael Ellerman
2024-04-12  5:10   ` Greg KH
2024-04-12  5:10     ` Greg KH

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=2025041646-resubmit-erasable-4386@gregkh \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.