From: Johannes Berg <johannes@sipsolutions.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: linux-next inclusion request for mac80211
Date: Tue, 17 Nov 2015 16:14:12 +0100 [thread overview]
Message-ID: <1447773252.14408.9.camel@sipsolutions.net> (raw)
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
next reply other threads:[~2015-11-17 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 15:14 Johannes Berg [this message]
2015-11-17 22:28 ` linux-next inclusion request for mac80211 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1447773252.14408.9.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).