All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Conor Dooley <Conor.Dooley@microchip.com>,
	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 riscv-soc-fixes tree
Date: Thu, 24 Oct 2024 23:52:26 +0100	[thread overview]
Message-ID: <20241024-pleading-grub-e50a759dc9c5@spud> (raw)
In-Reply-To: <20241025094819.5e01ddc5@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 550 bytes --]

On Fri, Oct 25, 2024 at 09:48:19AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the riscv-dt-fixes tree as a different
> commit (but the same patch):
> 
>   384f2024e1a1 ("MAINTAINERS: invert Misc RISC-V SoC Support's pattern")
> 
> This is commit
> 
>   7d9d88890f04 ("MAINTAINERS: invert Misc RISC-V SoC Support's pattern")
> 
> in the riscv-dt-fixes tree.

Ye, harmless. I found out the other day that this patch had not been
sent as a for v6.11-rcX. I'll drop it from one of the branches, thanks.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-10-24 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 22:48 linux-next: duplicate patch in the riscv-soc-fixes tree Stephen Rothwell
2024-10-24 22:52 ` Conor Dooley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-25 21:07 Stephen Rothwell
2024-02-25 21:52 ` Conor Dooley

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=20241024-pleading-grub-e50a759dc9c5@spud \
    --to=conor@kernel.org \
    --cc=Conor.Dooley@microchip.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 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.