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 2019-04-26
Date: Mon, 29 Apr 2019 11:02:26 -0400 (EDT) [thread overview]
Message-ID: <20190429.110226.845933624683233442.davem@davemloft.net> (raw)
In-Reply-To: <459c1807e264def23b14441777a6cda6e432bfc4.camel@sipsolutions.net>
From: Johannes Berg <johannes@sipsolutions.net>
Date: Mon, 29 Apr 2019 13:19:27 +0200
> Sorry to nag, and maybe I'm missing something, but I didn't see this
> show up in your tree, yet you marked it as accepted in patchwork:
>
> https://patchwork.ozlabs.org/patch/1091413/
>
> But maybe there's a gap that I should expect here, like you mark it as
> accepted when you start some kind of testing and then push it out later?
>
> Really the only reason I'm asking is that I wanted to forward to apply
> another patch, but maybe I'll ask you to apply that one patch directly.
Sorry about that, I'll use the excuse that I'm travelling :-)
I've pulled it in now and pushed it back out, should certainly be
there for sure now.
prev parent reply other threads:[~2019-04-29 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 9:07 pull-request: mac80211 2019-04-26 Johannes Berg
2019-04-29 11:19 ` Johannes Berg
2019-04-29 15:02 ` 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=20190429.110226.845933624683233442.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