linux-kernel - Re: linux-next inclusion request for mac80211

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] [day] [month] [year] [list]

Message-ID: <20151118092834.7956b883@canb.auug.org.au>
Date:	Wed, 18 Nov 2015 09:28:34 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	linux-wireless <linux-wireless@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: linux-next inclusion request for mac80211

Hi Johannes,

On Tue, 17 Nov 2015 16:14:12 +0100 Johannes Berg <johannes@...solutions.net> wrote:
>
> Could you please add my mac80211 and mac80211-next trees, found at
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git
> git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git
> 
> with their 'master' branches to linux-next?
> 
> These trees are feeding net and net-next respectively, but I don't
> always send them immediately and it'd be good to have early integration
> with other things happening elsewhere, in particular of course with the
> wifi drivers found in wireless-drivers{,-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 
sfr@...b.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/