From: Kalle Valo <kvalo@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>,
linux-wireless@vger.kernel.org, david.spinadel@intel.com,
ath10k@lists.infradead.org
Subject: Re: [PATCH v3 0/3] support ftm responder configuration/statistics
Date: Thu, 06 Sep 2018 19:18:24 +0300 [thread overview]
Message-ID: <87y3ce61m7.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1536250124.4015.10.camel@sipsolutions.net> (Johannes Berg's message of "Thu, 06 Sep 2018 18:08:44 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> On Thu, 2018-09-06 at 18:15 +0300, Kalle Valo wrote:
>>
>> Actually patch 3 made it:
>>
>> https://patchwork.kernel.org/patch/10590115/
>>
>> But it didn't get the rest as it says "Untitled series #15763".
>> Patchwork was timing out for me quite heavily so in that way I'm not
>> surprised that patches are getting lost :(
>
> No, it's not patchwork - I didn't get the patches (except for #3) via
> the list either.
Ah, missed that as the ath10k list did get all the patches. But very
good that patchwork was not to blame here.
--
Kalle Valo
next prev parent reply other threads:[~2018-09-06 20:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 1:01 [PATCH v3 0/3] support ftm responder configuration/statistics Pradeep Kumar Chitrapu
2018-09-06 1:01 ` [PATCH v3 2/3] mac80211: support FTM " Pradeep Kumar Chitrapu
2018-09-06 1:01 ` [PATCH v3 3/3] ath10k: Add support to configure ftm responder role Pradeep Kumar Chitrapu
2018-09-06 6:34 ` [PATCH v3 0/3] support ftm responder configuration/statistics Johannes Berg
2018-09-06 15:15 ` Kalle Valo
2018-09-06 16:08 ` Johannes Berg
2018-09-06 16:18 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-06 17:06 Pradeep Kumar Chitrapu
2018-09-06 19:58 ` Johannes Berg
2018-09-07 9:23 ` Arend van Spriel
2018-09-06 21:11 Pradeep Kumar Chitrapu
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=87y3ce61m7.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=david.spinadel@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pradeepc@codeaurora.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).