Hi Richard,
On Tue, 22 Jul 2014 08:52:21 +0200 Richard Weinberger <richard@xxxxxx> wrote:
>
> Am 22.07.2014 06:47, schrieb Stephen Rothwell:
> >
> > On Mon, 21 Jul 2014 16:02:46 +0200 Richard Weinberger <richard@xxxxxxxxxxxxx> wrote:
> >>
> >> The whole series can also be found at:
> >> git://git.kernel.org/pub/scm/linux/kernel/git/rw/misc.git signal_v4
> >>
> >> Andrew, can you please pickup this series?
> >
> > Why don't we just add that git tree to linux-next? Then you can send
> > Linus a pull request in the next merge window.
>
> That's a good idea.
> Can you please add the tree to linux-next?
Added from today. But I would prefer a more generic branch name if it
ever changes.
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@xxxxxxxxxxxxxxxx
Attachment:
signature.asc
Description: PGP signature
