From: Stanimir Varbanov <stanimir.k.varbanov@gmail.com>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Vikash Garodia <quic_vgarodia@quicinc.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.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
Subject: Re: [PATCH] media: venus: firmware: Use of_reserved_mem_lookup()
Date: Wed, 2 Aug 2023 14:55:21 +0300 [thread overview]
Message-ID: <21fad6fd-eddf-9edd-6dd8-58a32b9be9ef@gmail.com> (raw)
In-Reply-To: <ZMoak_qaUSX-pkP2@gerhold.net>
Hi Stephan,
On 2.08.23 г. 11:57 ч., Stephan Gerhold wrote:
> Hi Stanimir,
>
> I see that you already tagged the Venus updates for 6.6, but could you
> try to still apply this patch as well for 6.6? It's a requirement for
> some DT cleanup I'm working on and ideally needs to go in a kernel
> release earlier to avoid bisect problems.
>
> AFAICT it's been on the list for more than two months now with two
> Reviewed-by, so should be fine to just apply it. :)
>
Done, thanks for the reminder.
--
regards,
Stan
prev parent reply other threads:[~2023-08-02 11:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 18:16 [PATCH] media: venus: firmware: Use of_reserved_mem_lookup() Stephan Gerhold
2023-05-29 18:36 ` Konrad Dybcio
2023-05-29 18:43 ` Stephan Gerhold
2023-05-31 6:06 ` Vikash Garodia
2023-05-31 6:56 ` Stephan Gerhold
2023-05-31 7:34 ` Vikash Garodia
2023-05-31 7:45 ` Mukesh Ojha
2023-05-31 9:23 ` Stephan Gerhold
2023-05-31 8:55 ` Vikash Garodia
2023-08-02 8:57 ` Stephan Gerhold
2023-08-02 11:55 ` Stanimir Varbanov [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=21fad6fd-eddf-9edd-6dd8-58a32b9be9ef@gmail.com \
--to=stanimir.k.varbanov@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--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_vgarodia@quicinc.com \
--cc=stephan@gerhold.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