From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "Artem S. Tashkinov" <aros@gmx.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
chris.lu@mediatek.com, deren.wu@mediatek.com,
Peter Tsao <peter.tsao@mediatek.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>,
Linux kernel regressions list <regressions@lists.linux.dev>,
linux-mediatek <linux-mediatek@lists.infradead.org>
Subject: Re: BT_RAM_CODE_MT7961_1a_2_hdr.bin is missing in the firmware tree
Date: Wed, 24 Apr 2024 08:06:34 +0200 [thread overview]
Message-ID: <3b983390-110e-4c68-a825-6e811de78919@leemhuis.info> (raw)
In-Reply-To: <6574fc0f-8a24-4aff-8a1b-dbf960b6375d@gmx.com>
On 23.04.24 12:23, Artem S. Tashkinov wrote:
>
> Could you please push this firmware ASAP?
>
> It's been reported to be missing:
> https://bugzilla.kernel.org/show_bug.cgi?id=218757
FWIW, that can't be the only solution for that problem, as
Documentation/driver-api/firmware/firmware-usage-guidelines.rst clearly
states:
"""
Users switching to a newer kernel should *not* have to install newer
firmware files to keep their hardware working.
"""
Could anyone from mediatek please confirm that this rule is adhered?
Side note: I wonder if Peter's patch
https://lore.kernel.org/all/20240415141922.25055-1-peter.tsao@mediatek.com/
("Bluetooth: btusb: Fix the patch for MT7920 the affected to MT7921") is
relevant for this.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
parent reply other threads:[~2024-04-24 6:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6574fc0f-8a24-4aff-8a1b-dbf960b6375d@gmx.com>]
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=3b983390-110e-4c68-a825-6e811de78919@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=aros@gmx.com \
--cc=chris.lu@mediatek.com \
--cc=deren.wu@mediatek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=peter.tsao@mediatek.com \
--cc=regressions@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).