From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: PowerPC <linuxppc-dev@lists.ozlabs.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 powerpc tree
Date: Tue, 21 Jan 2025 16:42:01 +1100 [thread overview]
Message-ID: <87msfk4tau.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20250117174051.532c5772@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>
> 7fee0217538a ("MAINTAINERS: powerpc: Update my status")
>
> This is commit
>
> 77a903cd8e5a ("MAINTAINERS: powerpc: Update my status")
>
> in Linus' tree.
Sorry my fault. I asked Maddy to apply it without noticing that Linus
had already applied it.
cheers
next prev parent reply other threads:[~2025-01-21 5:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 6:40 linux-next: duplicate patch in the powerpc tree Stephen Rothwell
2025-01-21 5:42 ` Michael Ellerman [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-17 23:54 Stephen Rothwell
2024-07-18 4:32 ` Michael Ellerman
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=87msfk4tau.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.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