From: Christian Hewitt <christianshewitt@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Daniel Golle <daniel@makrotopia.org>
Subject: Re: [PATCH] wifi: mt7601u: check multiple firmware paths
Date: Tue, 2 Dec 2025 08:40:47 +0400 [thread overview]
Message-ID: <CD5CBB8A-2829-4436-9DA0-D1A88D594E92@gmail.com> (raw)
In-Reply-To: <20251201103529.1874a869@kernel.org>
> On 1 Dec 2025, at 10:35 pm, Jakub Kicinski <kuba@kernel.org> wrote:
>
> On Mon, 1 Dec 2025 09:03:36 +0000 Christian Hewitt wrote:
>> The linux-firmware repo moved mt7601u.bin from the root folder to
>> the mediatek sub-folder some time ago, but not all distros create
>> symlinks to the old location the driver checks. Update the driver
>> to check for firmware in both old and new locations.
>
> IDK.. 2.5 years ago.. how long is too long to wait for the distros
> to update their linux-firmware?
If compatibility with older firmware locations is no longer a concern the
previous patch submitted by Daniel is valid. If compatibility is desirable
this patch is valid. I’m not fussed which one gets merged, as long as
one of them is so the distro I maintain doesn’t need to patch the driver
to use the “new” location (our buildsystem doesn’t process WHENCE
which adds a symlink back to the old location the driver still uses).
Christian
prev parent reply other threads:[~2025-12-02 4:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 9:03 [PATCH] wifi: mt7601u: check multiple firmware paths Christian Hewitt
2025-12-01 18:35 ` Jakub Kicinski
2025-12-02 4:40 ` Christian Hewitt [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=CD5CBB8A-2829-4436-9DA0-D1A88D594E92@gmail.com \
--to=christianshewitt@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel@makrotopia.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).