Please add git://git.kernel.org/pub/scm/linux/kernel/git/borntraeger/linux.git linux-next

Please add git://git.kernel.org/pub/scm/linux/kernel/git/borntraeger/linux.git linux-next

[Christian Borntraeger]

Stephen,

can you add 
git://git.kernel.org/pub/scm/linux/kernel/git/borntraeger/linux.git linux-next
to linux-next?
It contains changes to ACCESS_ONCE and it would be good to have this cross tested on several platforms.
Thanks

Christian

Re: Please add git://git.kernel.org/pub/scm/linux/kernel/git/borntraeger/linux.git linux-next

[Stephen Rothwell]

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

Hi Christian,

On Thu, 04 Dec 2014 10:38:39 +0100 Christian Borntraeger <borntraeger@de.ibm.com> wrote:
>
> can you add 
> git://git.kernel.org/pub/scm/linux/kernel/git/borntraeger/linux.git linux-next
> to linux-next?
> It contains changes to ACCESS_ONCE and it would be good to have this cross tested on several platforms.
> Thanks

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 --]