Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1271308 > unrolled thread

linux-next inclusion request for mac80211

Back to article view | Back to linux.kernel

Contents

  linux-next inclusion request for mac80211 Johannes Berg <johannes@sipsolutions.net> - 2015-11-17 16:20 +0100
    Re: linux-next inclusion request for mac80211 Stephen Rothwell <sfr@canb.auug.org.au> - 2015-11-17 23:30 +0100

#1271308 — linux-next inclusion request for mac80211

Hi Stephen,

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}.

Thanks,
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1271702

Hi Johannes,

On Tue, 17 Nov 2015 16:14:12 +0100 Johannes Berg <johannes@sipsolutions.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@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web