From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
linux-media@vger.kernel.org
Cc: Javier Martinez Canillas <javierm@redhat.com>,
Vikash Garodia <vgarodia@qti.qualcomm.com>,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [GIT FIXES FOR v6.3] Venus fixes
Date: Thu, 2 Mar 2023 09:27:28 +0100 [thread overview]
Message-ID: <cb03d97f-ae48-4090-e14b-354373a2ebe3@leemhuis.info> (raw)
In-Reply-To: <20230302060413.67239-1-stanimir.k.varbanov@gmail.com>
On 02.03.23 07:04, Stanimir Varbanov wrote:
>
> This pull request includes a fix for regression in venus hardware reset.
> The reverted commit has been merged in v6.2.
>
> Please pull.
>
> regards,
> Stan
>
> The following changes since commit 3e62aba8284de0994a669d07983299242e68fe72:
>
> media: imx-mipi-csis: Check csis_fmt validity before use (2023-02-26 11:21:33 +0100)
>
> are available in the Git repository at:
>
> git://linuxtv.org/svarbanov/media_tree.git tags/tag-venus-fixes-for-v6.3
>
> for you to fetch changes up to 1440cfcf24db8c50d929d3c35ab6f87f868fa628:
>
> Revert "venus: firmware: Correct non-pix start and end addresses" (2023-03-02 07:52:10 +0200)
>
> ----------------------------------------------------------------
> Venus fixes for v6.3
>
> ----------------------------------------------------------------
> Javier Martinez Canillas (1):
> Revert "venus: firmware: Correct non-pix start and end addresses"
Good to see that this finally is heading towards mainline, thx.
What about the other venus regression[1] Javier provided this patch for:
https://patchwork.kernel.org/project/linux-media/patch/20230210081835.2054482-1-javierm@redhat.com/
[1] as pointed out earlier in
https://lore.kernel.org/all/87edq9hj4w.fsf@minerva.mail-host-address-is-not-set/
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.
#regzbot ^backmonitor:
https://lore.kernel.org/all/20230207102254.1446461-1-javierm@redhat.com/
next prev parent reply other threads:[~2023-03-02 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 6:04 [GIT FIXES FOR v6.3] Venus fixes Stanimir Varbanov
2023-03-02 8:27 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-03-13 14:28 ` Thorsten Leemhuis
2023-03-13 17:48 ` Stanimir Varbanov
2023-03-16 9:52 ` Linux regression tracking (Thorsten Leemhuis)
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=cb03d97f-ae48-4090-e14b-354373a2ebe3@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=javierm@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stanimir.k.varbanov@gmail.com \
--cc=vgarodia@qti.qualcomm.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).