Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1708391 > unrolled thread

clk-samsung tree inlcusion in linux-next

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  clk-samsung tree inlcusion in linux-next Sylwester Nawrocki <s.nawrocki@samsung.com> - 2017-08-10 12:10 +0200
    Re: clk-samsung tree inlcusion in linux-next Krzysztof Kozlowski <krzk@kernel.org> - 2017-08-10 12:50 +0200
    Re: clk-samsung tree inlcusion in linux-next Stephen Rothwell <sfr@canb.auug.org.au> - 2017-08-10 23:50 +0200

#1708391 — clk-samsung tree inlcusion in linux-next

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.


Thanks,
Sylwester

[toc] | [next] | [standalone]

#1708423

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

[toc] | [prev] | [next] | [standalone]

#1709046

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web