From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: "Regzbot (on behalf of Thorsten Leemhuis)" <regressions@leemhuis.info>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: Linux regressions report for mainline [2023-06-04]
Date: Sun, 4 Jun 2023 13:40:27 +0100 [thread overview]
Message-ID: <20230604134006.7c5c3f63@sal.lan> (raw)
In-Reply-To: <168588069830.1422846.3733273600224627850@leemhuis.info>
Em Sun, 4 Jun 2023 12:13:57 +0000
"Regzbot (on behalf of Thorsten Leemhuis)" <regressions@leemhuis.info> escreveu:
> Hi Linus. Nothing much to report for mainline, all business as usual. I
> had hoped Mauro would sent a pull with the media fixes, as they would
> contain one fix[1] for a bug that at least two people hit, but I guess
> it can wait another week.
>
> Ohh, and in case you care: the Logitech HID bug[3] from the 6.3 cycle
> was not really fixed[4] by commit 6199d23c91c or we dealt with two
> problems all the time (I guess it's the latter). But that will take a
> few days to sort out.
>
> [1] 14b4bd01f8e ("media: verisilicon: Additional fix for the crash when
> opening the driver")
We opted to use a different approach for the same bug [1]:
14b4bd01f8e5 ("media: verisilicon: Additional fix for the crash when opening the driver")
[1] https://lore.kernel.org/linux-media/e674cfcb-6b1b-8052-7f29-e0e97bdda3be@xs4all.nl/T/
Patch is already at linux-next. I'm sending the pull request in
a few, together with other fixes.
I was planning to send this earlier, but I got sick and had to take
some days off to recover my health.
Regards,
Mauro
prev parent reply other threads:[~2023-06-04 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 12:13 Regzbot (on behalf of Thorsten Leemhuis)
2023-06-04 12:40 ` Mauro Carvalho Chehab [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=20230604134006.7c5c3f63@sal.lan \
--to=mchehab@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®