public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Drew Fustini <fustini@kernel•org>
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: Wed, 5 Nov 2025 09:19:47 +1100	[thread overview]
Message-ID: <20251105091947.2692a796@canb.auug.org.au> (raw)
In-Reply-To: <aQpkDYXT3N6qWiZs@x1>

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

next prev parent reply	other threads:[~2025-11-04 22:19 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 [this message]
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=20251105091947.2692a796@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=arnd@arndb$(echo .)de \
    --cc=conor@kernel$(echo .)org \
    --cc=fustini@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox