[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57df6bed-3b74-df63-0c5c-7218aef8534b@gmail.com>
Date: Tue, 29 Mar 2022 23:33:04 +0200
From: Piotr Chmura <chmooreck@...il.com>
To: Thorsten Leemhuis <regressions@...mhuis.info>,
Antti Palosaari <crope@....fi>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Robert Schlabbach <robert_s@....net>
Cc: "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
az0123456@....de,
Linux Media Mailing List <linux-media@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Bug 215726 - si2157.c: mention name of the missing firmware file
It's supposed to be fixed by:
https://lore.kernel.org/linux-media/trinity-6009a608-b0ff-4e1a-9b91-ba4a97f10324-1648057812747@3c-app-gmx-bs71/T/#t
Test it please.
Best regards,
Piotr Chmura
W dniu 29.03.2022 o 10:33, Thorsten Leemhuis pisze:
> Hi, this is your Linux kernel regression tracker.
>
> I noticed a regression report in bugzilla.kernel.org that afaics nobody
> acted upon since it was reported about a week ago, that's why I decided
> to forward it to the lists and all people that seemed to be relevant
> here. To quote from https://bugzilla.kernel.org/show_bug.cgi?id=215726 :
>
>> I get the following error messages when trying to use si2157.ko in linux 5.17:
>> si2157 13-0060: found a 'Silicon Labs Si2157-A30 ROM 0x50'
>> si2157 13-0060: Can't continue without a firmware
>> I did work in linux 5.16.16 without a firmware file. Unfortunately the driver does not tell me the name of the missing firmware file.
> Could somebody take a look into this? Or was this discussed somewhere
> else already? Or even fixed?
>
> Anyway, to get this tracked:
>
> #regzbot introduced: v5.16..v5.17
> #regzbot from: az0123456@....de <az0123456@....de>
> #regzbot title: media: si2157.c: mention name of the missing firmware file
> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215726
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>
> P.S.: As the Linux kernel's regression tracker I'm getting a lot of
> reports on my table. I can only look briefly into most of them and lack
> knowledge about most of the areas they concern. I thus unfortunately
> will sometimes get things wrong or miss something important. I hope
> that's not the case here; if you think it is, don't hesitate to tell me
> in a public reply, it's in everyone's interest to set the public record
> straight.
>
Powered by blists - more mailing lists