public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Re: Add tenstorrent to linux-next
Date: Tue, 4 Nov 2025 17:10:11 -0800	[thread overview]
Message-ID: <aQqj8yBEUUxfqPA5@x1> (raw)
In-Reply-To: <20251105091947.2692a796@canb.auug.org.au>

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

  reply	other threads:[~2025-11-05  1:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 20:37 Add tenstorrent to linux-next Drew Fustini
2025-11-04 22:19 ` Stephen Rothwell
2025-11-05  1:10   ` Drew Fustini [this message]
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=aQqj8yBEUUxfqPA5@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