Add tenstorrent to linux-next

Add tenstorrent to linux-next

[Drew Fustini]

Hi Stephen,

I have setup device tree branches for Tenstorrent RISC-V SoCs, and I
would like to add them to linux-next for testing coverage. I have sent a
v6.19 PR to Arnd to add the Tenstorrent Blachkole SoC device tree [1].

tenstorrent-dt-fixes git https://github.com/tenstorrent/linux.git#tenstorrent-dt-fixes
tenstorrent-dt-for-next git https://github.com/tenstorrent/linux.git#tenstorrent-dt-for-next

Thanks,
Drew

[1] https://lore.kernel.org/linux-riscv/aPUemXdOFZEdkayE@x1/

Re: Add tenstorrent to linux-next

[Stephen Rothwell]

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

Hi Drew,

On Tue, 4 Nov 2025 12:37:33 -0800 Drew Fustini <fustini@kernel.org> wrote:
>
> I have setup device tree branches for Tenstorrent RISC-V SoCs, and I
> would like to add them to linux-next for testing coverage. I have sent a
> v6.19 PR to Arnd to add the Tenstorrent Blachkole SoC device tree [1].
> 
> tenstorrent-dt-fixes git https://github.com/tenstorrent/linux.git#tenstorrent-dt-fixes
> tenstorrent-dt-for-next git https://github.com/tenstorrent/linux.git#tenstorrent-dt-for-next

Added from today (I called the second "tenstorrent-dt").  I have just
you as contact so far - should I add anyone else?

Also, should I update your other trees (thead-clk, thead-clk-fixes,
thead-dt and thead-dt-fixes) to use your kernel.org address as contact?

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: Add tenstorrent to linux-next

[Drew Fustini]

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

On Wed, Nov 05, 2025 at 09:19:47AM +1100, Stephen Rothwell wrote:
> Hi Drew,
> 
> On Tue, 4 Nov 2025 12:37:33 -0800 Drew Fustini <fustini@kernel.org> wrote:
> >
> > I have setup device tree branches for Tenstorrent RISC-V SoCs, and I
> > would like to add them to linux-next for testing coverage. I have sent a
> > v6.19 PR to Arnd to add the Tenstorrent Blachkole SoC device tree [1].
> > 
> > tenstorrent-dt-fixes git https://github.com/tenstorrent/linux.git#tenstorrent-dt-fixes
> > tenstorrent-dt-for-next git https://github.com/tenstorrent/linux.git#tenstorrent-dt-for-next
> 
> Added from today (I called the second "tenstorrent-dt").  I have just
> you as contact so far - should I add anyone else?

Thank you. Yes, please add:

Joel Stanley <joel@jms.id.au>

> Also, should I update your other trees (thead-clk, thead-clk-fixes,
> thead-dt and thead-dt-fixes) to use your kernel.org address as contact?

Yes, please update my address to be fustini@kernel.org.

Thanks,
Drew

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

Re: Add tenstorrent to linux-next

[Stephen Rothwell]

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

Hi Drew,

On Tue, 4 Nov 2025 17:10:11 -0800 Drew Fustini <fustini@kernel.org> wrote:
>
> Thank you. Yes, please add:
> 
> Joel Stanley <joel@jms.id.au>

Done.

> > Also, should I update your other trees (thead-clk, thead-clk-fixes,
> > thead-dt and thead-dt-fixes) to use your kernel.org address as contact?  
> 
> Yes, please update my address to be fustini@kernel.org.

Done.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]