From: Drew Fustini <fustini@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <paul@pwsan.com>, "Arnd Bergmann" <arnd@arndb.de>,
"Clément Léger" <cleger@rivosinc.com>,
"Drew Fustini" <dfustini@oss.tenstorrent.com>,
"Himanshu Chauhan" <hchauhan@ventanamicro.com>,
"Lukas Bulwahn" <lukas.bulwahn@redhat.com>,
"Paul Walmsley" <pjw@kernel.org>,
ARM <linux-arm-kernel@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the risc-v tree with the arm-soc tree
Date: Wed, 26 Nov 2025 09:30:34 -0600 [thread overview]
Message-ID: <aScdGuUjxJ3FkwYg@gen8> (raw)
In-Reply-To: <20251126094511.07bdf834@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2259 bytes --]
On Wed, Nov 26, 2025 at 09:45:11AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the risc-v tree got a conflict in:
>
> MAINTAINERS
>
> between commit:
>
> 4de28f1edcfb ("dt-bindings: riscv: Add Tenstorrent Blackhole compatible")
>
> from the arm-soc tree and commits:
>
> e0ce62cfe3a9 ("drivers: firmware: add riscv SSE support")
> 832fd6c2e55c ("MAINTAINERS: refer to intended files in RISC-V SSE DRIVER")
>
> 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.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc MAINTAINERS
> index aacd4a754dab,6fa1048c248a..000000000000
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@@ -22247,15 -22195,14 +22254,23 @@@ F: arch/riscv/boot/dts/spacemit
> N: spacemit
> K: spacemit
>
> + RISC-V SSE DRIVER
> + M: Clément Léger <cleger@rivosinc.com>
> + R: Himanshu Chauhan <himanshu@thechauhan.dev>
> + L: linux-riscv@lists.infradead.org
> + S: Maintained
> + F: drivers/firmware/riscv/riscv_sbi_sse.c
> + F: include/linux/riscv_sbi_sse.h
> +
> +RISC-V TENSTORRENT SoC SUPPORT
> +M: Drew Fustini <dfustini@oss.tenstorrent.com>
> +M: Joel Stanley <jms@oss.tenstorrent.com>
> +L: linux-riscv@lists.infradead.org
> +S: Maintained
> +T: git https://github.com/tenstorrent/linux.git
> +F: Documentation/devicetree/bindings/riscv/tenstorrent.yaml
> +F: arch/riscv/boot/dts/tenstorrent/
> +
> RISC-V THEAD SoC SUPPORT
> M: Drew Fustini <fustini@kernel.org>
> M: Guo Ren <guoren@kernel.org>
Thanks for fixing this up. It looks like the correct resolution to me.
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/tenstorrent/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 --]
next prev parent reply other threads:[~2025-11-26 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 22:45 linux-next: manual merge of the risc-v tree with the arm-soc tree Stephen Rothwell
2025-11-26 15:30 ` Drew Fustini [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-24 22:12 Stephen Rothwell
2021-01-24 22:12 ` Stephen Rothwell
2021-01-25 9:44 ` Arnd Bergmann
2021-01-25 9:44 ` Arnd Bergmann
2021-02-14 21:09 ` Stephen Rothwell
2021-02-14 21:09 ` Stephen Rothwell
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=aScdGuUjxJ3FkwYg@gen8 \
--to=fustini@kernel.org \
--cc=arnd@arndb.de \
--cc=cleger@rivosinc.com \
--cc=dfustini@oss.tenstorrent.com \
--cc=hchauhan@ventanamicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul@pwsan.com \
--cc=pjw@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.