From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull-request: mac80211 2016-01-26
Date: Thu, 28 Jan 2016 16:06:17 -0800 (PST) [thread overview]
Message-ID: <20160128.160617.1926761912082289010.davem@davemloft.net> (raw)
In-Reply-To: <1453806034-10185-1-git-send-email-johannes@sipsolutions.net>
From: Johannes Berg <johannes@sipsolutions.net>
Date: Tue, 26 Jan 2016 12:00:33 +0100
> After split up the patches from the previous pull request that was
> lost in the process, here's a new one with fixes for the current
> cycle (I'll follow up with a -next one later.)
>
> I've also scripted my pull-request sending process a bit more, so
> hopefully the emails will no longer have any unexpected UTF-8 contents
> that tripped up patchwork :)
>
> Let me know if there's any problem.
Pulled, thanks Johannes.
prev parent reply other threads:[~2016-01-29 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 11:00 pull-request: mac80211 2016-01-26 Johannes Berg
2016-01-29 0:06 ` David Miller [this message]
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=20160128.160617.1926761912082289010.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johannes@sipsolutions.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 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).