public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Drew Fustini <fustini@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
	soc@kernel.org, "Palmer Dabbelt" <palmer@dabbelt.com>,
	"Paul Walmsley" <paul@pwsan.com>, "Joel Stanley" <joel@jms.id.au>,
	"Clément Léger" <cleger@rivosinc.com>,
	"Drew Fustini" <dfustini@oss.tenstorrent.com>,
	"Himanshu Chauhan" <hchauhan@ventanamicro.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Paul Walmsley" <pjw@kernel.org>
Subject: Re: linux-next: manual merge of the risc-v tree with the tenstorrent-dt tree
Date: Wed, 19 Nov 2025 15:54:31 -0800	[thread overview]
Message-ID: <aR5Yt2x2JRx7gK/r@x1> (raw)
In-Reply-To: <20251120102925.57ab2fe7@canb.auug.org.au>

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

On Thu, Nov 20, 2025 at 10:29:25AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the risc-v tree got a conflict in:
> 
>   MAINTAINERS
> 
> between commits:
> 
>   4de28f1edcfb ("dt-bindings: riscv: Add Tenstorrent Blackhole compatible")
>   8e88602e99a7 ("riscv: dts: Add Tenstorrent Blackhole SoC PCIe cards")
> 
> from the tenstorrent-dt tree and commit:
> 
>   5ffe60d26107 ("drivers: firmware: add riscv SSE support")
> 
> from the risc-v tree.
> 
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.

Thank you for fixing it up. The resolution looks correct to me. The
Tenstorrent MAINTAINERS patch is in the tag tenstorrent-dt-for-v6.19 [1]
that I used for the 6.19 pull request [2].

Drew

[1] https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git/tag/?h=tenstorrent-dt-for-v6.19
[2] https://lore.kernel.org/all/aPUemXdOFZEdkayE@x1/

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

      reply	other threads:[~2025-11-19 23:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 23:29 linux-next: manual merge of the risc-v tree with the tenstorrent-dt tree Stephen Rothwell
2025-11-19 23:54 ` Drew Fustini [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=aR5Yt2x2JRx7gK/r@x1 \
    --to=fustini@kernel.org \
    --cc=arnd@arndb.de \
    --cc=cleger@rivosinc.com \
    --cc=dfustini@oss.tenstorrent.com \
    --cc=hchauhan@ventanamicro.com \
    --cc=joel@jms.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul@pwsan.com \
    --cc=pjw@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=soc@kernel.org \
    /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