public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Zong-Zhe Yang <kevin_yang@realtek.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"raja.mani@oss.qualcomm.com" <raja.mani@oss.qualcomm.com>
Subject: RE: [PATCH v2 3/6] iw: util: support parsing link id
Date: Fri, 19 Sep 2025 12:12:53 +0000	[thread overview]
Message-ID: <7c988e7cbffc4edb8d8e863e2f1c82cc@realtek.com> (raw)
In-Reply-To: <f4e33ca572e77755c6db82a37c5372a99a8b7485.camel@sipsolutions.net>

Johannes Berg <johannes@sipsolutions.net> wrote:
> On Wed, 2025-09-17 at 13:55 +0800, Zong-Zhe Yang wrote:
> > For NL80211_FLAG_MLO_VALID_LINK_ID cases, MLD needs to assign link id,
> > but non-MLD doesn't. Add support of parsing link id where the pattern
> > is as below.
> >
> >       [link-id <LINK ID>]
> >
> > If found, put NL80211_ATTR_MLO_LINK_ID and remove the assignment from
> > the argv range.
> >
> > +     memmove(argv + pos, argv + pos + 2,
> > +             sizeof(*argv) * (*argc - pos - 2));
> 
> Honestly, I don't really like this, it's a bit too magic? What if you have something in there that
> is like
> 
>  ... ssid link-id foo bar
> 
> and then it *meant* the SSID to be "link-id", but with this it now actually fails or so? I don't
> think it's a good idea.

I missed to consider this kind of cases, sorry.

> 
> So I think it should just be parsing it where it is at the beginning, and then for the last patch
> just put it at the beginning in the help, call parse_link_id() first like you did already, and we
> don't get any such potential mixups?
> 

Thanks. I think it works.
I will send v3, which turns to parse link-id field at the beginning of argv.


  reply	other threads:[~2025-09-19 12:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17  5:55 [PATCH v2 0/6] iw: support EHT and link id for setting bitrate Zong-Zhe Yang
2025-09-17  5:55 ` [PATCH v2 1/6] iw: update nl80211.h Zong-Zhe Yang
2025-09-17  5:55 ` [PATCH v2 2/6] iw: info: extended features print EHT beacon rate Zong-Zhe Yang
2025-09-17  5:55 ` [PATCH v2 3/6] iw: util: support parsing link id Zong-Zhe Yang
2025-09-19 10:33   ` Johannes Berg
2025-09-19 12:12     ` Zong-Zhe Yang [this message]
2025-09-17  5:55 ` [PATCH v2 4/6] iw: bitrate: refactor description Zong-Zhe Yang
2025-09-17  5:55 ` [PATCH v2 5/6] iw: bitrate: support EHT rate/gi/ltf Zong-Zhe Yang
2025-09-17  5:55 ` [PATCH v2 6/6] iw: bitrate: support link id Zong-Zhe Yang

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=7c988e7cbffc4edb8d8e863e2f1c82cc@realtek.com \
    --to=kevin_yang@realtek.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=raja.mani@oss.qualcomm.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