From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the driver-core.current tree
Date: Fri, 12 Apr 2024 14:36:25 +1000 [thread overview]
Message-ID: <87mspzci46.fsf@mail.lhotse> (raw)
In-Reply-To: <20240412084310.035f018d@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> The following commit is also in the powerpc-fixes tree as a different
> commit (but the same patch):
>
> 156539fd6501 ("Documentation: embargoed-hardware-issues.rst: Add myself for Power")
>
> This is commit
>
> 36627111b568 ("Documentation: embargoed-hardware-issues.rst: Add myself for Power")
>
> in the powerpc-fixes tree.
I can drop my version easily enough.
cheers
next prev parent reply other threads:[~2024-04-12 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 22:43 linux-next: duplicate patch in the driver-core.current tree Stephen Rothwell
2024-04-12 4:36 ` Michael Ellerman [this message]
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=87mspzci46.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).