Skip to contentSkip to conversation

Add tenstorrent to linux-next

DISCUSSION Drew Fustini 2 participants 4 messages Nov 4, 2025 – Nov 5, 2025 Linux-next tree

lore
Share & tools
lore
#0 lore raw

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/

#1 lore raw

Hi Drew,

Quoted 7 lines · On Tue, 4 Nov 2025 12:37:33 -0800 Drew Fustini <[email protected]> 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.

Signature · 3 lines
Cheers,
Stephen Rothwell 
[email protected]
#2 lore raw
Quoted 8 lines · Stephen Rothwell

Hi Drew,

Quoted 5 lines · On Tue, 4 Nov 2025 12:37:33 -0800 Drew Fustini <[email protected]> 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].

Quoted 5 lines
Quoted 2 lines

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 <[email protected]>

Quoted 2 lines

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 [email protected].

Thanks,
Drew

#3 lore raw

Hi Drew,

Quoted 4 lines · On Tue, 4 Nov 2025 17:10:11 -0800 Drew Fustini <[email protected]> wrote:

Thank you. Yes, please add:

Joel Stanley <[email protected]>

Done.

Quoted 4 lines
Quoted 2 lines

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 [email protected].

Done.

Signature · 2 lines
Cheers,
Stephen Rothwell