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 2018-01-15
Date: Tue, 16 Jan 2018 14:30:08 -0500 (EST) [thread overview]
Message-ID: <20180116.143008.770895612140000630.davem@davemloft.net> (raw)
In-Reply-To: <20180115105154.9727-1-johannes@sipsolutions.net>
From: Johannes Berg <johannes@sipsolutions.net>
Date: Mon, 15 Jan 2018 11:51:53 +0100
> I know this comes last minute, so if it doesn't make it then
> I guess we can live with that, but I got the earliest of the
> patches here on Wednesday last week, and that was the most
> uninteresting one - the others didn't come in until Saturday.
>
> Please pull and let me know if there's any problem.
Pulled, thanks Johannes.
prev parent reply other threads:[~2018-01-16 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 10:51 pull-request: mac80211 2018-01-15 Johannes Berg
2018-01-16 19:30 ` 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=20180116.143008.770895612140000630.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).