public inbox for linux-next@vger.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 patches in the riscv-dt tree
Date: Thu, 15 Jan 2026 15:20:38 +0000	[thread overview]
Message-ID: <20260115-finally-thinness-771557fd8822@spud> (raw)
In-Reply-To: <20260114120537.0b55d4ef@canb.auug.org.au>

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

On Wed, Jan 14, 2026 at 12:05:37PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> The following commits are also in the riscv-dt-fixes tree as different
> commits (but the same patches):
> 
>   a36b2aaae742 ("dt-bindings: riscv: extensions: Drop unnecessary select schema")
>   fff010c776f7 ("dt-bindings: riscv: update ratified version of h, svinval, svnapot, svpbmt")
> 
> These are commits
> 
>   eb766d282af7 ("dt-bindings: riscv: extensions: Drop unnecessary select schema")
>   6f5d8490ca03 ("dt-bindings: riscv: update ratified version of h, svinval, svnapot, svpbmt")
> 
> in the riscv-dt-fixes tree.

I think this may have been bad timing, I moved these from one tree to
the other around about when you work on -next.

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

      reply	other threads:[~2026-01-15 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14  1:05 linux-next: duplicate patches in the riscv-dt tree Stephen Rothwell
2026-01-15 15:20 ` Conor Dooley [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=20260115-finally-thinness-771557fd8822@spud \
    --to=conor@kernel$(echo .)org \
    --cc=Conor.Dooley@microchip$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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