Re: [PATCH v5] Add JSON output options to 'iw' for scan results

Jeff Johnson
2024-03-05T17:47:45Z

On 3/5/2024 8:35 AM, Aditya Kumar Singh wrote:
> On 3/5/24 21:25, Jeff Johnson wrote:
>> On 3/5/2024 1:41 AM, Johannes Berg wrote:
>>> On Mon, 2024-03-04 at 23:01 +0300, Isaev Ruslan wrote:
>>>> v5 changes:
>>>> - add json print to print_ap_channel_report()
>>>> - minor refactor open_json_object()
>>>
>>> Alright, yay, so mechanical submission issues out of the way, this looks
>>> readable :)
>>
>>
>> Did the v5 version hit the list? I don't see it, and neither does lore:
>> <https://lore.kernel.org/all/5c5be485dcfceb44fc731e47758d6be3.legale.legale@gmail.com/>
>>
>> I received v4 directly, not via the list, and that was addressed to
>> "Undisclosed Recipients". lore also doesn't have v4:
>> <https://lore.kernel.org/all/8a0ba4b33aedd96f303db7cfe966b83b.legale.legale@gmail.com/>
>>
>> So I don't think the mechanical submission issues are out of the way
>> unless the list rejected the patch due to size, which seems unlikely.
>>
>
> Yes it did -
> https://patchwork.kernel.org/project/linux-wireless/patch/d9739fa6d3dd085587c4f413087dfd6c.legale.legale@gmail.com/
>
> Looks like the first reply started a separate thread. Probably
> --in-reply-to was missed.
>

Very strange. There is obviously still some Message-Id: strangeness
since the patchwork message id (and lore message id)
"d9739fa6d3dd085587c4f413087dfd6c.legale.legale@gmail.com" doesn't match
the In-Reply-To message id in Johannes' reply
"5c5be485dcfceb44fc731e47758d6be3.legale.legale@gmail.com"

Perhaps the patch was sent to Johannes as a separate unicast message
that was separate from the message sent to the list?

/jeff