public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Piotr Chmura <chmooreck@gmail.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
	Antti Palosaari <crope@iki.fi>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Robert Schlabbach <robert_s@gmx.net>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	az0123456@gmx.de,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Bug 215726 - si2157.c: mention name of the missing firmware file
Date: Tue, 29 Mar 2022 23:33:04 +0200	[thread overview]
Message-ID: <57df6bed-3b74-df63-0c5c-7218aef8534b@gmail.com> (raw)
In-Reply-To: <5f660108-8812-383c-83e4-29ee0558d623@leemhuis.info>

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@gmx.de <az0123456@gmx.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.
>


      parent reply	other threads:[~2022-03-29 21:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29  8:33 Bug 215726 - si2157.c: mention name of the missing firmware file Thorsten Leemhuis
2022-03-29 19:21 ` Robert Schlabbach
2022-03-30  9:55   ` Thorsten Leemhuis
2022-03-30 10:35     ` Piotr Chmura
2022-03-30 10:44       ` Thorsten Leemhuis
2022-03-30 15:47         ` Piotr Chmura
2022-03-31  6:46           ` Thorsten Leemhuis
2022-03-29 21:33 ` Piotr Chmura [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=57df6bed-3b74-df63-0c5c-7218aef8534b@gmail.com \
    --to=chmooreck@gmail.com \
    --cc=az0123456@gmx.de \
    --cc=crope@iki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=robert_s@gmx.net \
    /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