From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Artur Rojek <artur@conclusive.pl>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Jakub Klama <jakub@conclusive.pl>,
Wojciech Kloska <wojciech@conclusive.pl>,
Ulf Axelsson <ulf.axelsson@nordicsemi.no>,
Josh Boyer <jwboyer@kernel.org>
Subject: Re: [RFC PATCH v2 0/2] wifi: Nordic nRF70 series
Date: Mon, 28 Apr 2025 10:45:59 +0200 [thread overview]
Message-ID: <9a657c02-b688-4f2f-bb0b-fd25d19a54be@broadcom.com> (raw)
In-Reply-To: <4854f6a248fdc501d4157339fdb21f9a3ca3097d.camel@sipsolutions.net>
+ 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.
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.
Regards,
Arend
next prev parent reply other threads:[~2025-04-28 8:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 17:59 [RFC PATCH v2 0/2] wifi: Nordic nRF70 series Artur Rojek
2025-04-22 17:59 ` [RFC PATCH v2 1/2] dt-bindings: wifi: Add support for Nordic nRF70 Artur Rojek
2025-04-25 10:38 ` Krzysztof Kozlowski
2025-04-22 17:59 ` [RFC PATCH v2 2/2] wifi: Add Nordic nRF70 series Wi-Fi driver Artur Rojek
2025-04-24 15:07 ` Johannes Berg
2025-04-25 16:49 ` Artur Rojek
2025-04-25 18:09 ` Johannes Berg
2025-05-01 10:34 ` Artur Rojek
2025-04-25 19:31 ` Christophe JAILLET
2025-05-01 10:41 ` Artur Rojek
2025-05-01 17:44 ` Christophe JAILLET
2025-04-25 18:11 ` [RFC PATCH v2 0/2] wifi: Nordic nRF70 series Johannes Berg
2025-04-28 8:45 ` Arend van Spriel [this message]
2025-04-28 17:10 ` Josh Boyer
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=9a657c02-b688-4f2f-bb0b-fd25d19a54be@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=artur@conclusive.pl \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jakub@conclusive.pl \
--cc=johannes@sipsolutions.net \
--cc=jwboyer@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=ulf.axelsson@nordicsemi.no \
--cc=wojciech@conclusive.pl \
/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