public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Aditya Kumar Singh <quic_adisi@quicinc.com>,
	Jeff Johnson <quic_jjohnson@quicinc.com>,
	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, 05 Mar 2024 17:40:51 +0100	[thread overview]
Message-ID: <c8b3ede515d22a9d3b7ecc1c72b7a7ebd730b43d.camel@sipsolutions.net> (raw)
In-Reply-To: <e873f69e-e4b8-4dd0-a54a-191e9826ab56@quicinc.com>

On Tue, 2024-03-05 at 22:05 +0530, Aditya Kumar Singh wrote:
> 
> 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.
> 

No, somehow I got two copies in my inbox, the first of which hadn't made
it to the list for some reason, but I didn't notice in time that it
hadn't ... Sorry.

johannes

  reply	other threads:[~2024-03-05 16:41 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
2024-03-05 16:40       ` Johannes Berg [this message]
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=c8b3ede515d22a9d3b7ecc1c72b7a7ebd730b43d.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=legale.legale@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_adisi@quicinc.com \
    --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