Linux wireless drivers development
 help / color / mirror / Atom feed
From: Aditya Kumar Singh <quic_adisi@quicinc.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>, <ath12k@lists.infradead.org>
Subject: Re: [PATCH] wifi: mac80211: fix assigning channel in activate links
Date: Tue, 1 Oct 2024 12:50:36 +0530	[thread overview]
Message-ID: <5baec254-9fe9-4923-ba38-c43bb9300508@quicinc.com> (raw)
In-Reply-To: <06708838017266efd2351f0bda1bf01b0ee2bef9.camel@sipsolutions.net>

On 10/1/24 12:02, Johannes Berg wrote:
> On Tue, 2024-10-01 at 09:45 +0530, Aditya Kumar Singh wrote:
>> The current flow in _ieee80211_set_active_links() does not align with the
>> operational requirements of drivers that groups multiple hardware
>> under a single wiphy.
> 
> Btw, given that, I'd argue it's not really "fix ..." right now, since
> there's no such driver and no real bug? Dunno. But "fix" makes it sound
> like there's a bugfix, and it isn't now, it's just preparing for future
> ath12k compatibility.
> 

I see your point. Sure will rephrase the message and will not use 'fix' 
word in next version.

-- 
Aditya


      reply	other threads:[~2024-10-01  7:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01  4:15 [PATCH] wifi: mac80211: fix assigning channel in activate links Aditya Kumar Singh
2024-10-01  6:31 ` Johannes Berg
2024-10-01  7:17   ` Aditya Kumar Singh
2024-10-01  7:22     ` Johannes Berg
2024-10-01  7:37       ` Aditya Kumar Singh
2024-10-01  8:08         ` Johannes Berg
2024-10-01  8:26           ` Aditya Kumar Singh
2024-10-01  8:28             ` Johannes Berg
2024-10-01  9:16               ` Aditya Kumar Singh
2024-10-01  6:32 ` Johannes Berg
2024-10-01  7:20   ` Aditya Kumar Singh [this message]

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=5baec254-9fe9-4923-ba38-c43bb9300508@quicinc.com \
    --to=quic_adisi@quicinc.com \
    --cc=ath12k@lists.infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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