From: Drew Fustini <fustini@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Conor Dooley <conor@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Add tenstorrent to linux-next
Date: Tue, 4 Nov 2025 12:37:33 -0800 [thread overview]
Message-ID: <aQpkDYXT3N6qWiZs@x1> (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/
next reply other threads:[~2025-11-04 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 20:37 Drew Fustini [this message]
2025-11-04 22:19 ` Add tenstorrent to linux-next Stephen Rothwell
2025-11-05 1:10 ` Drew Fustini
2025-11-05 3:37 ` 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=aQpkDYXT3N6qWiZs@x1 \
--to=fustini@kernel.org \
--cc=arnd@arndb.de \
--cc=conor@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).