From: Vikash Garodia <vgarodia@qti.qualcomm.com>
To: "bryan.odonoghue@linaro.org" <bryan.odonoghue@linaro.org>,
"Viswanath Boma (Temp) (QUIC)" <quic_vboma@quicinc.com>,
"stanimir.varbanov@linaro.org" <stanimir.varbanov@linaro.org>,
"Vikash Garodia (QUIC)" <quic_vgarodia@quicinc.com>,
Andy Gross <agross@kernel.org>,
"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Dikshita Agarwal <dikshita@qti.qualcomm.com>
Subject: RE: [PATCH] venus: Enable sufficient sequence change support for sc7180 and fix for Decoder STOP command issue.
Date: Thu, 16 Mar 2023 16:26:38 +0000 [thread overview]
Message-ID: <DM8PR02MB816977D65272F628547187D0F3BC9@DM8PR02MB8169.namprd02.prod.outlook.com> (raw)
In-Reply-To: <e3805411-170a-759b-3608-7f53464641e8@linaro.org>
Hi Bryan,
>-----Original Message-----
>From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
>Sent: Thursday, March 16, 2023 5:24 PM
>To: Viswanath Boma (Temp) (QUIC) <quic_vboma@quicinc.com>;
>stanimir.varbanov@linaro.org; Vikash Garodia (QUIC)
><quic_vgarodia@quicinc.com>; Andy Gross <agross@kernel.org>;
>bjorn.andersson@linaro.org; Konrad Dybcio <konrad.dybcio@linaro.org>;
>Mauro Carvalho Chehab <mchehab@kernel.org>; linux-media@vger.kernel.org;
>linux-arm-msm@vger.kernel.org; linux-kernel@vger.kernel.org
>Cc: Vikash Garodia <vgarodia@qti.qualcomm.com>; Dikshita Agarwal
><dikshita@qti.qualcomm.com>
>Subject: Re: [PATCH] venus: Enable sufficient sequence change support for
>sc7180 and fix for Decoder STOP command issue.
>
>WARNING: This email originated from outside of Qualcomm. Please be wary of
>any links or attachments, and do not enable macros.
>
>On 16/03/2023 08:15, quic_vboma@quicinc.com wrote:
>> + if (IS_V4(core))
>
>Hi Viswanath,
>
>Could you please take in the change to base on on IRIS version and rebase your
>patch on _that_ much at least, not necessarily all of the changes in the series
>below. Dikshita should be able help.
Let have this fix go separately and not tie this with the AR50LT series. This fix is a pending
for sometime due to delay in raising the pull request. Working with Stan to get the pull
request raised in next couple of days.
>https://lore.kernel.org/linux-arm-msm/c9c324aa-6192-f878-9189-
>635626e76b13@quicinc.com/
>
>IRIS version is more granular/accurate than V4/V6 etc.
>
>---
>bod
next prev parent reply other threads:[~2023-03-16 16:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 12:12 [PATCH 0/1] Fix for VP9 DRC and Decoder STOP issue quic_vboma
2022-11-15 12:12 ` [PATCH 1/1] venus: Enable sufficient sequence change support for sc7180 and Fix for Decoder STOP command issue quic_vboma
2022-12-02 0:54 ` Nathan Hebert
2022-12-02 1:03 ` Bryan O'Donoghue
2023-02-02 6:47 ` [PATCH V2 0/1] Fix for VP9 DRC and Decoder STOP issue quic_vboma
2023-02-02 6:47 ` [PATCH V2 1/1] venus: Enable sufficient sequence change support for sc7180 and fix for Decoder STOP command issue quic_vboma
2023-02-02 10:10 ` Dmitry Baryshkov
2023-02-03 4:24 ` Viswanath Boma (Temp)
2023-03-16 10:27 ` Dmitry Baryshkov
2023-03-23 9:19 ` Viswanath Boma (Temp)
2023-03-16 8:15 ` [PATCH V3 0/1] Fix for VP9 DRC and Decoder STOP issue quic_vboma
2023-03-16 8:15 ` [PATCH] venus: Enable sufficient sequence change support for sc7180 and fix for Decoder STOP command issue quic_vboma
2023-03-16 10:20 ` Dmitry Baryshkov
2023-03-23 9:16 ` Viswanath Boma (Temp)
2023-03-23 16:18 ` Konrad Dybcio
2023-03-16 11:53 ` Bryan O'Donoghue
2023-03-16 16:26 ` Vikash Garodia [this message]
2023-03-16 8:41 ` [PATCH V3 0/1] Fix for VP9 DRC and Decoder STOP issue Konrad Dybcio
2023-03-16 12:37 ` Dmitry Baryshkov
2023-03-23 9:22 ` Viswanath Boma (Temp)
2023-03-23 9:37 ` Dmitry Baryshkov
2023-02-02 10:02 ` [PATCH V2 " Dmitry Baryshkov
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=DM8PR02MB816977D65272F628547187D0F3BC9@DM8PR02MB8169.namprd02.prod.outlook.com \
--to=vgarodia@qti.qualcomm.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=dikshita@qti.qualcomm.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=quic_vboma@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
--cc=stanimir.varbanov@linaro.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®