* Re: clk-samsung tree inlcusion in linux-next
2017-08-10 10:07 ` clk-samsung tree inlcusion in linux-next Sylwester Nawrocki
@ 2017-08-10 10:46 ` Krzysztof Kozlowski
2017-08-10 21:45 ` Stephen Rothwell
1 sibling, 0 replies; 3+ messages in thread
From: Krzysztof Kozlowski @ 2017-08-10 10:46 UTC (permalink / raw)
To: Sylwester Nawrocki
Cc: Stephen Rothwell, linux-samsung-soc, Linux Kernel Mailing List,
Chanwoo Choi, Tomasz Figa, Stephen Boyd, Mike Turquette
On Thu, Aug 10, 2017 at 12:07 PM, Sylwester Nawrocki
<s.nawrocki@samsung.com> wrote:
> Hi Stephen,
>
> I'd like to ask for inclusion of this (clk-samsung) tree in linux-next:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/snawrocki/clk.git for-next
>
> It will contain Samsung SoC clock controller related patches.
Cool, finally! :)
BR,
Krzysztof
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: clk-samsung tree inlcusion in linux-next
2017-08-10 10:07 ` clk-samsung tree inlcusion in linux-next Sylwester Nawrocki
2017-08-10 10:46 ` Krzysztof Kozlowski
@ 2017-08-10 21:45 ` Stephen Rothwell
1 sibling, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2017-08-10 21:45 UTC (permalink / raw)
To: Sylwester Nawrocki
Cc: linux-samsung-soc, Linux Kernel Mailing List,
Krzysztof Kozlowski, Chanwoo Choi, Tomasz Figa, Stephen Boyd,
Mike Turquette
Hi Sylwester,
On Thu, 10 Aug 2017 12:07:31 +0200 Sylwester Nawrocki <s.nawrocki@samsung.com> wrote:
>
> I'd like to ask for inclusion of this (clk-samsung) tree in linux-next:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/snawrocki/clk.git for-next
>
> It will contain Samsung SoC clock controller related patches.
Added from today.
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
^ permalink raw reply [flat|nested] 3+ messages in thread