* Add Thunderbolt tree to linux-next
@ 2018-12-05 11:37 Mika Westerberg
2018-12-05 22:31 ` Stephen Rothwell
0 siblings, 1 reply; 2+ messages in thread
From: Mika Westerberg @ 2018-12-05 11:37 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Linux-Next, linux-kernel, Greg Kroah-Hartman, Andreas Noever,
Michael Jamet, Mika Westerberg, Yehezkel Bernat, Lukas Wunner
Hi Stephen,
I maintain the Thunderbolt tree that gets merged to mainline via Greg's
char-misc tree. I would like to get the tree included in linux-next to
get wider coverage before it hits Greg's tree.
Can you please include branches 'fixes' and 'next' from:
git://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git
in linux-next?
Thanks!
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: Add Thunderbolt tree to linux-next
2018-12-05 11:37 Add Thunderbolt tree to linux-next Mika Westerberg
@ 2018-12-05 22:31 ` Stephen Rothwell
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2018-12-05 22:31 UTC (permalink / raw)
To: Mika Westerberg
Cc: Linux-Next, linux-kernel, Greg Kroah-Hartman, Andreas Noever,
Michael Jamet, Yehezkel Bernat, Lukas Wunner
[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]
Hi Mika,
On Wed, 5 Dec 2018 13:37:36 +0200 Mika Westerberg <mika.westerberg@linux•intel.com> wrote:
>
> I maintain the Thunderbolt tree that gets merged to mainline via Greg's
> char-misc tree. I would like to get the tree included in linux-next to
> get wider coverage before it hits Greg's tree.
>
> Can you please include branches 'fixes' and 'next' from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git
>
> in linux-next?
Added from today (well the fixes tree will be added tomorrow - but it
was empty anyway).
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 --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-12-05 22:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-12-05 11:37 Add Thunderbolt tree to linux-next Mika Westerberg
2018-12-05 22:31 ` Stephen Rothwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox