Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <50d2dd83079d01e1c260590cd5470e3a534b4a66.camel@sipsolutions.net>
Subject: Re: [PATCH 1/2] wifi: cfg80211: remove scan_width support
From:   Johannes Berg <johannes@sipsolutions.net>
To:     Jeff Johnson <quic_jjohnson@quicinc.com>,
        linux-wireless@vger.kernel.org
Cc:     Xinyue Ling <quic_xinyling@quicinc.com>
Date:   Tue, 29 Aug 2023 18:24:49 +0200
In-Reply-To: <5b809506-7fea-4598-b6ae-39ea94cc2849@quicinc.com>
References: <20230829121742.634a0631eaf3.I38b5dcce8b130f93743a2d43ab9d89269b937b5d@changeid>
         <5b809506-7fea-4598-b6ae-39ea94cc2849@quicinc.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
MIME-Version: 1.0
Precedence: bulk

On Tue, 2023-08-29 at 09:21 -0700, Jeff Johnson wrote:
> Just want to remind that there were two proposals given to allow setting=
=20
> this from upstream:
> <https://lore.kernel.org/all/20230301090242.1613672-1-quic_xinyling@quici=
nc.com/>
>=20
> In the thread you asked for additional information:
> <https://lore.kernel.org/all/6796c3c209a071983d330ca145d7ab8b929d53c6.cam=
el@sipsolutions.net/>

Yes, I know. I figured it was long enough ago :P

> So to see if there is any update on that request Cc: Xinyue Ling=20
> <quic_xinyling@quicinc.com>

Sure.

> Would hate to see this ripped out just to need to replace it later.

I actually wouldn't mind that much. I have a gut feeling that at least
the mac80211 part will actually not be of any use to Qualcomm since most
of the things I see these days are for non-upstream drivers anyway.

Therefore, it would actually make sense to understand how this could be
done properly _without_ supporting it in mac80211, because it's clear
that just adding support for it as proposed in those patches will break
in mac80211 pretty badly.

If we even decide to go that route, because honestly, I'm getting pretty
upset about the whole Qualcomm adding various APIs that we never see any
users for, then not maintaining it, _and_ complaining that we don't fix
things upstream quickly enough.

johannes