From: Aloka Dixit <alokad@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211: Add radiotap channel flag option for 6GHz band
Date: Sun, 20 Sep 2020 11:59:26 -0700 [thread overview]
Message-ID: <0d0174377e9aa0e7be118a8dca6826eb@codeaurora.org> (raw)
In-Reply-To: <87zh5v1pv4.fsf@tynnyri.adurom.net>
On 2020-09-11 23:16, Kalle Valo wrote:
> Aloka Dixit <alokad@codeaurora.org> writes:
>
>> On 2020-09-11 13:39, Johannes Berg wrote:
>>> On Fri, 2020-09-11 at 20:39 +0000, Aloka Dixit wrote:
>>>> Radiotap header needs a new channel flag for 6GHz packets.
>>>> This change uses value 0x200 for new enum balue for 6GHz which was
>>>> previously used for passsive scan flag but has since been removed.
>>>
>>> You can't just add to radiotap in a kernel patch ...
>>>
>>> But also, just today I replied elsewhere saying that we don't really
>>> need a flag at all?
>>>
>>> johannes
>>
>> Somehow your reply to other patch didn't show up on the patchwork,
>> don't know why :-)
>
> Oh, this is making me worry. I do see Johannes' reply on the list:
>
> https://lore.kernel.org/linux-wireless/1cc7242cd00cd5141a56f17a7f5c80700485aa39.camel@sipsolutions.net/
>
> But like you said, there's still nothing on the patchwork (even after
> 23h):
>
> https://patchwork.kernel.org/patch/11769643/
>
> I hope this is just a temporary glitch, but if this happens again
> please
> do let me know about any patchwork problems. It will create major
> problems for us if patchwork starts losing mail.
This is still happening, even your reply did not show up on the RFC
patch here:
https://patchwork.kernel.org/patch/11771491/
next prev parent reply other threads:[~2020-09-20 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <010101747ee4b985-86863ec8-33e2-4f78-9d9b-93110bfa29fc-000000@us-west-2.amazonses.com>
2020-09-11 20:39 ` [RFC] mac80211: Add radiotap channel flag option for 6GHz band Johannes Berg
2020-09-11 20:45 ` Aloka Dixit
2020-09-12 6:16 ` Kalle Valo
2020-09-20 18:59 ` Aloka Dixit [this message]
2020-09-21 9:10 ` Kalle Valo
[not found] ` <010101747eea5fbb-4c045b3e-1db2-44aa-b093-8f621da60b43-000000@us-west-2.amazonses.com>
2020-09-11 20:46 ` Johannes Berg
2020-09-11 20:39 Aloka Dixit
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=0d0174377e9aa0e7be118a8dca6826eb@codeaurora.org \
--to=alokad@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.