From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Networking <netdev@vger.kernel.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 usb.current tree
Date: Wed, 10 Apr 2024 07:50:59 +0200 [thread overview]
Message-ID: <2024041043-sprain-stank-10af@gregkh> (raw)
In-Reply-To: <20240410090500.4018b9a0@canb.auug.org.au>
On Wed, Apr 10, 2024 at 09:05:00AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the net tree as a different commit
> (but the same patch):
>
> fbdd90334a62 ("MAINTAINERS: Drop Li Yang as their email address stopped working")
>
> This is commit
>
> eaac25d026a1 ("MAINTAINERS: Drop Li Yang as their email address stopped working")
>
> in the net tree.
That's fine, this should merge without an issue.
thanks for letting us know.
greg k-h
prev parent reply other threads:[~2024-04-10 5:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 23:05 linux-next: duplicate patch in the usb.current tree Stephen Rothwell
2024-04-10 5:50 ` Greg KH [this message]
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=2024041043-sprain-stank-10af@gregkh \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).