linux-kernel - Re: at91 git tree in linux-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 23 Aug 2018 09:30:45 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Nicolas Ferre <nicolas.ferre@...rochip.com>
Cc:     Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Ludovic Desroches <ludovic.desroches@...rochip.com>,
        <ksummit-discuss@...ts.linuxfoundation.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: at91 git tree in linux-next

Hi all,

On Wed, 22 Aug 2018 14:47:56 +0200 Nicolas Ferre <nicolas.ferre@...rochip.com> wrote:
>
> Alexandre Ludovic and myself are the group of maintainers for Microchip 
> ARM SoCs. The current tree that we have in linux-next is mine [1] and we 
> are moving to a common group kernel.org tree.
> 
> So, can you please add our new tree to linux-next:
> at91 git 
> git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-next
> 
> instead of:
> git://git.kernel.org/pub/scm/linux/kernel/git/nferre/linux-at91.git#at91-next
> 
> In addition to that, we also have now a "fixes" branch. Can you please 
> add it to your "fixes" tree?
> 
> at91 git 
> git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-fixes
> 
> Thanks for your help, best regards,
>    Nicolas
> 
> 
> [1] 
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Next/Trees#n84

All done.  I added Alexandre and Ludovic as contacts for both trees as
well.

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@...b.auug.org.au

Content of type "application/pgp-signature" skipped