From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
Vikash Garodia <quic_vgarodia@quicinc.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: quic_renjiang@quicinc.com, quic_vnagar@quicinc.com,
quic_dikshita@quicinc.com, konradybcio@kernel.org,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Stanimir Varbanov <stanimir.varbanov@linaro.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] media: venus: Add support for static video encoder/decoder declarations
Date: Wed, 27 Nov 2024 01:36:14 +0000 [thread overview]
Message-ID: <ce9ac473-2f73-4c7a-97b1-08be39f3adb4@linaro.org> (raw)
In-Reply-To: <20241127-media-staging-24-11-25-rb3-hw-compat-string-v1-1-99c16f266b46@linaro.org>
On 27/11/2024 01:34, Bryan O'Donoghue wrote:
> + dev_info(dev, "Node %s exists won't create new\n", node_name);
Bah I meant to remove this before sending.
---
bod
next prev parent reply other threads:[~2024-11-27 1:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 1:34 [PATCH 0/3] media: venus: Provide support for selecting encoder/decoder from in-driver Bryan O'Donoghue
2024-11-27 1:34 ` [PATCH 1/3] media: venus: Add support for static video encoder/decoder declarations Bryan O'Donoghue
2024-11-27 1:36 ` Bryan O'Donoghue [this message]
2024-11-28 20:02 ` Konrad Dybcio
2024-11-28 22:14 ` Bryan O'Donoghue
2024-11-28 22:34 ` Bryan O'Donoghue
2024-11-29 11:23 ` Konrad Dybcio
2024-11-29 11:41 ` Bryan O'Donoghue
2024-11-27 1:34 ` [PATCH 2/3] media: venus: Populate video encoder/decoder nodename entries Bryan O'Donoghue
2024-11-27 1:34 ` [PATCH 3/3] media: dt-bindings: qcom-venus: Deprecate video-decoder and video-encoder where applicable Bryan O'Donoghue
2024-11-27 9:03 ` Krzysztof Kozlowski
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=ce9ac473-2f73-4c7a-97b1-08be39f3adb4@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.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_dikshita@quicinc.com \
--cc=quic_renjiang@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
--cc=quic_vnagar@quicinc.com \
--cc=robh@kernel.org \
--cc=stanimir.k.varbanov@gmail.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