From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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, 8 Jan 2025 09:15:12 +0100 [thread overview]
Message-ID: <2025010854-annoying-splurge-8f67@gregkh> (raw)
In-Reply-To: <20250108070228.1067a48c@canb.auug.org.au>
On Wed, Jan 08, 2025 at 07:02:28AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>
> b4aee757f1ba ("MAINTAINERS: align Danilo's maintainer entries")
>
> This is commit
>
> 2872e21c47c3 ("MAINTAINERS: align Danilo's maintainer entries")
>
> in Linus' tree.
Ah, I missed that Linus had already picked it up, sorry. Merging should
be fine.
thanks,
greg k-h
next prev parent reply other threads:[~2025-01-08 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 20:02 linux-next: duplicate patch in the driver-core.current tree Stephen Rothwell
2025-01-08 8:15 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-15 23:44 Stephen Rothwell
2025-04-16 5:49 ` Greg KH
2024-04-11 22:43 Stephen Rothwell
2024-04-12 4:36 ` Michael Ellerman
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=2025010854-annoying-splurge-8f67@gregkh \
--to=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox