Add kdbus branch to linux-next?

Add kdbus branch to linux-next?

[Greg KH]

Hi Stephen,

Can you add the:
	https://git.kernel.org/cgit/linux/kernel/git/gregkh/char-misc.git/ kdbus

tree to linux-next so that it gets the normal amount of testing that
linux-next provides?

The code has been reworked and reviewed many times, and this last round
seems to have no objections, so I'm queueing it up to be merged for
4.1-rc1.

thanks,

greg k-h

Re: Add kdbus branch to linux-next?

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]

Hi Greg,

On Sun, 15 Mar 2015 10:34:52 +0100 Greg KH <gregkh@linuxfoundation.org> wrote:
>
> Can you add the:
> 	https://git.kernel.org/cgit/linux/kernel/git/gregkh/char-misc.git/ kdbus
> 
> tree to linux-next so that it gets the normal amount of testing that
> linux-next provides?
> 
> The code has been reworked and reviewed many times, and this last round
> seems to have no objections, so I'm queueing it up to be merged for
> 4.1-rc1.

Added from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment 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: 819 bytes --]