Re: [RFC] mac80211: Add radiotap channel flag option for 6GHz band

[Kalle Valo <kvalo@codeaurora.org>]

Aloka Dixit <alokad@codeaurora.org> writes:

> 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/

Aloka's original email (with the patch) had the id:

Message-ID: <010101747ee4b989-1d670a2f-a032-4f64-aa65-3847a5951522-000000@us-west-2.amazonses.com>

But Johannes' reply referenced different id:

In-Reply-To: <010101747ee4b985-86863ec8-33e2-4f78-9d9b-93110bfa29fc-000000@us-west-2.amazonses.com>
References: <010101747ee4b985-86863ec8-33e2-4f78-9d9b-93110bfa29fc-000000@us-west-2.amazonses.com>

And this is why patchwork cannot detect that the replies are to Aloka's
patch. I suspect smtp.codeaurora.org is to blame here, I have seen it
messing with message ids before so this would not be the first time this
is happening.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches