* Add tenstorrent clk to linux-next
@ 2026-03-10 23:17 Drew Fustini
2026-03-11 0:16 ` Mark Brown
0 siblings, 1 reply; 2+ messages in thread
From: Drew Fustini @ 2026-03-10 23:17 UTC (permalink / raw)
To: Mark Brown; +Cc: linux-next, linux-kernel, Conor Dooley, Arnd Bergmann
Hi Mark,
I have setup clk branches in the Tenstorrent repo on kernel.org as we
will now maintain drivers for the clock controllers in our new Atlantis
SoC. Please add them to linux-next:
tenstorrent-clk https://git.kernel.org/pub/scm/linux/kernel/git/tenstorrent/linux.git#tenstorrent-clk-for-next
tenstorrent-clk-fixes https://git.kernel.org/pub/scm/linux/kernel/git/tenstorrent/linux.git#tenstorrent-clk-fixes
Also, please update the existing tenstorrent-dt entries to use the
kernel.org repo instead of github:
tenstorrent-dt https://git.kernel.org/pub/scm/linux/kernel/git/tenstorrent/linux.git#tenstorrent-dt-for-next
tenstorrent-dt-fixes https://git.kernel.org/pub/scm/linux/kernel/git/tenstorrent/linux.git#tenstorrent-dt-fixes
Thanks,
Drew
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Add tenstorrent clk to linux-next
2026-03-10 23:17 Add tenstorrent clk to linux-next Drew Fustini
@ 2026-03-11 0:16 ` Mark Brown
0 siblings, 0 replies; 2+ messages in thread
From: Mark Brown @ 2026-03-11 0:16 UTC (permalink / raw)
To: Drew Fustini; +Cc: linux-next, linux-kernel, Conor Dooley, Arnd Bergmann
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]
On Tue, Mar 10, 2026 at 04:17:52PM -0700, Drew Fustini wrote:
> I have setup clk branches in the Tenstorrent repo on kernel.org as we
> will now maintain drivers for the clock controllers in our new Atlantis
> SoC. Please add them to linux-next:
> tenstorrent-clk https://git.kernel.org/pub/scm/linux/kernel/git/tenstorrent/linux.git#tenstorrent-clk-for-next
> tenstorrent-clk-fixes https://git.kernel.org/pub/scm/linux/kernel/git/tenstorrent/linux.git#tenstorrent-clk-fixes
These will appear from tomorrow all being well.
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.
> Also, please update the existing tenstorrent-dt entries to use the
> kernel.org repo instead of github:
> tenstorrent-dt https://git.kernel.org/pub/scm/linux/kernel/git/tenstorrent/linux.git#tenstorrent-dt-for-next
> tenstorrent-dt-fixes https://git.kernel.org/pub/scm/linux/kernel/git/tenstorrent/linux.git#tenstorrent-dt-fixes
Done..
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-03-11 0:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-10 23:17 Add tenstorrent clk to linux-next Drew Fustini
2026-03-11 0:16 ` Mark Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox