Hi Doug, On Wed, 27 May 2015 09:13:29 -0400 Doug Ledford <dledf...@redhat.com> wrote: > > Stephen, can you set it up so that the linux-next tag from > git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma.git is added > to the linux-next testing please?
I haven't fetched tags in the past, only branches (it is a little
tricky, but I can work on it) and there is no linux-next tag in that
tree anyway (I assume that you mean for-next).
Also, how does this relate to Roland's infiniband tree
(git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git#for-next)
that is already in linux-next?
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
s...@canb.auug.org.au
pgpwzMf1pUkqU.pgp
Description: OpenPGP digital signature
