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-next next-2019-10-11
Date: Sun, 13 Oct 2019 11:29:37 -0700 (PDT) [thread overview]
Message-ID: <20191013.112937.1593993262080277258.davem@davemloft.net> (raw)
In-Reply-To: <20191011085736.15772-1-johannes@sipsolutions.net>
From: Johannes Berg <johannes@sipsolutions.net>
Date: Fri, 11 Oct 2019 10:57:35 +0200
> Let me try to be a bit "maintainer-of-the-day agnostic" ;-)
>
> I'll be going on vacation, but figured I'd at least get this
> stuff out. As usual, I ran the hwsim tests from wpa_s/hostapd
> and all looks fine, compilation also was OK.
>
> Kalle has agreed to help cover when I'm on vacation (though
> I'm home next week, so if there's any fallout I'll deal with
> it then), so if there's something urgent he may include some
> stack changes in his trees or ask you to or apply a patch.
This is fine, thanks for the heads up.
> Please pull and let me know if there's any problem.
Pulled, thanks Johannes.
prev parent reply other threads:[~2019-10-13 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 8:57 pull-request: mac80211-next next-2019-10-11 Johannes Berg
2019-10-13 18:29 ` 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=20191013.112937.1593993262080277258.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).