From: Rob Herring <robh@kernel.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: andersson@kernel.org, agross@kernel.org,
konrad.dybcio@linaro.org, mturquette@baylibre.com,
sboyd@kernel.org, dmitry.baryshkov@linaro.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
jonathan@marek.ca, quic_tdas@quicinc.com,
vladimir.zapolskiy@linaro.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v4 3/4] media: dt-bindings: media: camss: Add qcom,sc8280xp-camss binding
Date: Fri, 13 Oct 2023 09:09:21 -0500 [thread overview]
Message-ID: <20231013140921.GA3773179-robh@kernel.org> (raw)
In-Reply-To: <20231012113100.3656480-4-bryan.odonoghue@linaro.org>
On Thu, Oct 12, 2023 at 12:30:59PM +0100, Bryan O'Donoghue wrote:
> Add bindings for qcom,sc8280xp-camss in order to support the camera
> subsystem for sc8280xp as found in the Lenovo x13s Laptop.
You don't need 2 'media' in the subject.
>
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> This patch depends-on:
> https://lore.kernel.org/lkml/20231004161853.86382-2-bryan.odonoghue@linaro.org/T
Who is supposed to apply the above and this patch? Normally, this would
go thru the media tree, but you didn't send it to them or the media
list. You did Cc the clock maintainers which seems weird on its own, but
I suppose based on the bot error that's because the above patch is a
clock patch. But why would the clock maintainers care about this one. I
can only guess your intent is for all of this to be merged thru the QCom
tree. We shouldn't have to sort thru these series and guess though. You
should state that unless you really don't know, but I'd expect you've
been around long enough to know.
Rob
next prev parent reply other threads:[~2023-10-13 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 11:30 [PATCH v4 0/4] Add sc8280xp CCI and CAMSS core dtsi Bryan O'Donoghue
2023-10-12 11:30 ` [PATCH v4 1/4] arm64: dts: qcom: sc8280xp: Add in CAMCC for sc8280xp Bryan O'Donoghue
2023-10-21 23:02 ` kernel test robot
2023-10-12 11:30 ` [PATCH v4 2/4] arm64: dts: qcom: sc8280xp: camss: Add CCI definitions Bryan O'Donoghue
2023-10-12 11:30 ` [PATCH v4 3/4] media: dt-bindings: media: camss: Add qcom,sc8280xp-camss binding Bryan O'Donoghue
2023-10-12 12:24 ` Rob Herring
2023-10-13 14:09 ` Rob Herring [this message]
2023-10-13 15:56 ` Bryan O'Donoghue
2023-10-12 11:31 ` [PATCH v4 4/4] arm64: dts: qcom: sc8280xp: camss: Add CAMSS block definition Bryan O'Donoghue
2023-11-18 0:51 ` [PATCH v4 0/4] Add sc8280xp CCI and CAMSS core dtsi Konrad Dybcio
2023-11-18 11:29 ` Bryan O'Donoghue
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=20231013140921.GA3773179-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=jonathan@marek.ca \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_tdas@quicinc.com \
--cc=sboyd@kernel.org \
--cc=vladimir.zapolskiy@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;
as well as URLs for NNTP newsgroup(s).