From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@nbd.name>,
Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] wifi: cfg80211: check radio iface combination for multi radio per wiphy
Date: Wed, 11 Sep 2024 18:00:28 +0200 [thread overview]
Message-ID: <d880275455b93c92a0f8d0e59169a22433d815ba.camel@sipsolutions.net> (raw)
In-Reply-To: <3d2d9a9e-43ee-46f5-bf66-6227ce6bdfd7@nbd.name>
On Wed, 2024-09-11 at 17:58 +0200, Felix Fietkau wrote:
> >
> > We still need the part of the patch that calls the validation on each
> > radio, but it shouldn't be different from the global one. If you could
> > make that patch I'd appreciate it.
>
> It's implemented the way we discussed it back when this topic came up.
> Legacy user space gets the ifcomb data from the first radio for
> compatibility. The actual global ifcomb data is reported in a new attribute.
>
Hah, I forgot about that. Then that means we _do_ need to relax the
validation in this case, but I guess needs to come with a big comment
saying how the driver-global != nl80211 global ...
Sorry!
johannes
next prev parent reply other threads:[~2024-09-11 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 11:29 [PATCH v3] wifi: cfg80211: check radio iface combination for multi radio per wiphy Karthikeyan Periyasamy
2024-09-11 9:42 ` Johannes Berg
2024-09-11 12:51 ` Karthikeyan Periyasamy
2024-09-11 12:52 ` Johannes Berg
2024-09-11 13:15 ` Karthikeyan Periyasamy
2024-09-11 13:40 ` Johannes Berg
2024-09-11 15:21 ` Karthikeyan Periyasamy
2024-09-11 15:25 ` Johannes Berg
2024-09-11 15:58 ` Felix Fietkau
2024-09-11 16:00 ` Johannes Berg [this message]
2024-09-11 15:59 ` Karthikeyan Periyasamy
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=d880275455b93c92a0f8d0e59169a22433d815ba.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=quic_periyasa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.