linux-kernel - Re: [RFC PATCH v2 0/2] wifi: Nordic nRF70 series

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+5PVA76ZT_NEe_xeoc55V0p7M4W8KneAPjUR78ja0q3aBUZ8A@mail.gmail.com>
Date: Mon, 28 Apr 2025 13:10:11 -0400
From: Josh Boyer <jwboyer@...nel.org>
To: Arend van Spriel <arend.vanspriel@...adcom.com>
Cc: Johannes Berg <johannes@...solutions.net>, Artur Rojek <artur@...clusive.pl>, 
	Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, 
	Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>, 
	Sascha Hauer <s.hauer@...gutronix.de>, linux-wireless@...r.kernel.org, 
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Jakub Klama <jakub@...clusive.pl>, Wojciech Kloska <wojciech@...clusive.pl>, 
	Ulf Axelsson <ulf.axelsson@...dicsemi.no>
Subject: Re: [RFC PATCH v2 0/2] wifi: Nordic nRF70 series

On Mon, Apr 28, 2025 at 4:46 AM Arend van Spriel
<arend.vanspriel@...adcom.com> wrote:
>
> + Josh
>
> On 4/25/2025 8:11 PM, Johannes Berg wrote:
> > On Tue, 2025-04-22 at 19:59 +0200, Artur Rojek wrote:
> >> 1) Nordic gave us permission to upstream the firmware blob [1] required
> >>     to use this driver. As that needs to go through separate
> >>     linux-firmware repository and is subject to different licensing,
> >>     should I try to upstream it in parallel with this series, or does it
> >>     need to wait until the kernel driver gets in?
> >
> > I have no idea. Chicken and egg, I guess.

Parallel is fine.

> It used to be a check by the linux-firmware maintainer if the firmware
> blob is referenced in kernel module info. I assume the main linux tree
> is checked and not linux-next.

Eh.  We check for net-new firmware just to make sure we aren't growing
the repo for something that will never be used by an in-tree driver,
but if the driver is in linux-next that's good enough.

josh