From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Javier Martinez Canillas <javierm@redhat.com>,
Vikash Garodia <vgarodia@qti.qualcomm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mka@chromium.org" <mka@chromium.org>
Cc: Albert Esteve <aesteve@redhat.com>,
"stanimir.varbanov@linaro.org" <stanimir.varbanov@linaro.org>,
Enric Balletbo i Serra <eballetb@redhat.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
"Vikash Garodia (QUIC)" <quic_vgarodia@quicinc.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Fritz Koenig <frkoenig@google.com>,
"Dikshita Agarwal (QUIC)" <quic_dikshita@quicinc.com>,
"Rajeshwar Kurapaty (QUIC)" <quic_rkurapat@quicinc.com>
Subject: Re: [PATCH] Revert "venus: firmware: Correct non-pix start and end addresses"
Date: Wed, 15 Feb 2023 11:53:26 +0100 [thread overview]
Message-ID: <ea283f0a-ca72-447e-ce87-68c1bbee793e@leemhuis.info> (raw)
In-Reply-To: <6f97a117-0d9c-e21b-9adf-50f2233ba9e3@leemhuis.info>
On 11.02.23 15:27, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 10.02.23 11:07, Javier Martinez Canillas wrote:
>> On 2/10/23 10:22, Vikash Garodia wrote:
>>
>>>> So what should we do about this folks? Since not allowing the driver to probe on
>>>> at least SC7180 is a quite serious regression, can we revert for now until a proper
>>>> fix is figured out?
>>>
>>> I am able to repro this issue on sc7180 and discussing with firmware team on the cause
>>> of reset failure. The original patch was raised for fixing rare SMMU faults during warm
>>> boot of video hardware. Hence looking to understand the regressing part before we
>>> proceed to revert.
>>
>> Great, if you are working on a proper fix then that would be much better indeed.
>
> Yeah, that's great, but OTOH: there is almost certainly just one week
> before 6.2 will be released. Ideally this should be fixed by then.
> Vikash, do you think that's in the cards? If not: why not revert this
> now to make sure 6.2 works fine?
Hmm, no reply. And we meanwhile have Wednesday and 6.2 is almost
certainly going to be out on Sunday. And the problem was called "a quite
serious regression" above. So why not quickly fix this with the revert,
as proposed earlier?
Vikash? Javier?
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 ignore-activity
next prev parent reply other threads:[~2023-02-15 10:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 10:22 [PATCH] Revert "venus: firmware: Correct non-pix start and end addresses" Javier Martinez Canillas
2023-02-07 16:40 ` Vikash Garodia
2023-02-07 17:50 ` mka
2023-02-07 22:39 ` mka
2023-02-08 9:06 ` Javier Martinez Canillas
2023-02-10 8:15 ` Javier Martinez Canillas
2023-02-10 9:22 ` Vikash Garodia
2023-02-10 10:07 ` Javier Martinez Canillas
2023-02-11 14:27 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-15 10:53 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-02-15 10:57 ` Javier Martinez Canillas
2023-02-15 13:18 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-21 15:03 ` Thorsten Leemhuis
2023-02-23 5:45 ` Vikash Garodia
2023-02-23 8:05 ` Javier Martinez Canillas
2023-02-28 16:03 ` Javier Martinez Canillas
[not found] ` <d18fac76-6b77-a446-5fe0-7236556e9187@quicinc.com>
[not found] ` <0c84724d-08d4-ddcb-5f71-4eb8261240c6@quicinc.com>
2023-03-06 10:43 ` Javier Martinez Canillas
2023-04-01 20:53 ` Leonard Lausen
2023-04-02 5:02 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-03 0:27 ` Leonard Lausen
2023-04-03 6:32 ` 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=ea283f0a-ca72-447e-ce87-68c1bbee793e@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=aesteve@redhat.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=eballetb@redhat.com \
--cc=frkoenig@google.com \
--cc=javierm@redhat.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mka@chromium.org \
--cc=quic_dikshita@quicinc.com \
--cc=quic_rkurapat@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
--cc=regressions@lists.linux.dev \
--cc=stanimir.k.varbanov@gmail.com \
--cc=stanimir.varbanov@linaro.org \
--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