Received-SPF: pass (google.com: domain of linux-wireless+bounces-1541-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Message-ID: <b39657b8e248443b1b728e81fd194942a02826d8.camel@sipsolutions.net>
Subject: Re: [PATCH] iw: strip NLA_FLAGS from printed bands
From: Johannes Berg <johannes@sipsolutions.net>
To: Matthias May <matthias.may@westermo.com>, 
	"linux-wireless@vger.kernel.org"
	 <linux-wireless@vger.kernel.org>
Cc: Zefir Kurtisi <Zefir.Kurtisi@westermo.com>
Date: Fri, 05 Jan 2024 21:36:52 +0100
In-Reply-To: <728b6538-19b3-4fb4-b91e-f72080c4c9f0@westermo.com>
References: <20231221222842.1310957-1-matthias.may@westermo.com>
	 <6a54a2afd9e2b1b67822e3ca9b86654e3886feef.camel@sipsolutions.net>
	 <728b6538-19b3-4fb4-b91e-f72080c4c9f0@westermo.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.50.2 (3.50.2-1.fc39) 
Precedence: bulk
MIME-Version: 1.0

On Fri, 2024-01-05 at 21:35 +0100, Matthias May wrote:
> We saw that happen on one of our platforms where we are forced to use an=
=20
> out-of-tree driver by QCA (SPF12.2).
> If you think this is something that can not happen with upstream=20
> drivers, feel free to ignore this patch.
>=20

It should be independent of drivers, so they must have modified cfg80211
to explicitly use the nla_put_nested() instead of
nla_put_nested_noflag()? It's just ... weird.

johannes