From: Aditya Kumar Singh <quic_adisi@quicinc.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>,
Johannes Berg <johannes@sipsolutions.net>,
Isaev Ruslan <legale.legale@gmail.com>,
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v5] Add JSON output options to 'iw' for scan results
Date: Tue, 5 Mar 2024 22:05:30 +0530 [thread overview]
Message-ID: <e873f69e-e4b8-4dd0-a54a-191e9826ab56@quicinc.com> (raw)
In-Reply-To: <7eec23f3-5e1d-4787-bba3-6b06549db091@quicinc.com>
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.
next prev parent reply other threads:[~2024-03-05 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5c5be485dcfceb44fc731e47758d6be3.legale.legale@gmail.com>
2024-03-05 9:41 ` [PATCH v5] Add JSON output options to 'iw' for scan results Johannes Berg
2024-03-05 10:17 ` Nicolas Escande
2024-03-05 10:31 ` Johannes Berg
2024-03-05 11:32 ` Isaev Ruslan
2024-03-05 13:29 ` Johannes Berg
2024-03-05 11:19 ` Isaev Ruslan
2024-03-05 15:55 ` Jeff Johnson
2024-03-05 16:35 ` Aditya Kumar Singh [this message]
2024-03-05 16:40 ` Johannes Berg
2024-03-05 17:47 ` Jeff Johnson
2024-03-04 20:01 Isaev Ruslan
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=e873f69e-e4b8-4dd0-a54a-191e9826ab56@quicinc.com \
--to=quic_adisi@quicinc.com \
--cc=johannes@sipsolutions.net \
--cc=legale.legale@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
/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