From: Johannes Berg <johannes@sipsolutions.net>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull-request: mac80211 2018-09-03
Date: Mon, 03 Sep 2018 14:19:30 +0200 [thread overview]
Message-ID: <1535977170.3437.62.camel@sipsolutions.net> (raw)
In-Reply-To: <20180903121546.27673-1-johannes@sipsolutions.net> (sfid-20180903_141604_430542_42638ACE)
On Mon, 2018-09-03 at 14:15 +0200, Johannes Berg wrote:
> Hi Dave,
>
> This time around for mac80211 I have a larger than usual number of
> fixes, in part because Luca dumped our (Intel's) patches out after
> quite a while - we'll try to make sure this doesn't happen again.
>
> Shortlog below, as usual, each fix is pretty self-contained but it
> adds up to quite a bit overall.
>
> Please pull and let me know if there's any problem.
Oh, forgot: if/when you merge this, could you pull it into net-next at
some point? I have a patch that depends on this but isn't really net
material - it can wait though, so no hurry.
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull-request: mac80211 2018-09-03
Date: Mon, 03 Sep 2018 14:19:30 +0200 [thread overview]
Message-ID: <1535977170.3437.62.camel@sipsolutions.net> (raw)
In-Reply-To: <20180903121546.27673-1-johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> (sfid-20180903_141604_430542_42638ACE)
On Mon, 2018-09-03 at 14:15 +0200, Johannes Berg wrote:
> Hi Dave,
>
> This time around for mac80211 I have a larger than usual number of
> fixes, in part because Luca dumped our (Intel's) patches out after
> quite a while - we'll try to make sure this doesn't happen again.
>
> Shortlog below, as usual, each fix is pretty self-contained but it
> adds up to quite a bit overall.
>
> Please pull and let me know if there's any problem.
Oh, forgot: if/when you merge this, could you pull it into net-next at
some point? I have a patch that depends on this but isn't really net
material - it can wait though, so no hurry.
johannes
next prev parent reply other threads:[~2018-09-03 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 12:15 pull-request: mac80211 2018-09-03 Johannes Berg
2018-09-03 12:15 ` Johannes Berg
2018-09-03 12:19 ` Johannes Berg [this message]
2018-09-03 12:19 ` Johannes Berg
2018-09-04 5:12 ` David Miller
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=1535977170.3437.62.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.