From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Anusha Rao <quic_anusha@quicinc.com>
Cc: agross@kernel.org, andersson@kernel.org,
bhupesh.sharma@linaro.org, conor+dt@kernel.org,
davem@davemloft.net, devicetree@vger.kernel.org,
herbert@gondor.apana.org.au, konrad.dybcio@linaro.org,
krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, mturquette@baylibre.com,
p.zabel@pengutronix.de, quic_arajkuma@quicinc.com,
quic_gokulsri@quicinc.com, quic_kathirav@quicinc.com,
quic_poovendh@quicinc.com, quic_sjaganat@quicinc.com,
quic_srichara@quicinc.com, robh+dt@kernel.org, sboyd@kernel.org,
thara.gopinath@gmail.com
Subject: Re: [PATCH V4 3/4] dt-bindings: qcom-qce: add SoC compatible string for ipq9574
Date: Fri, 23 Jun 2023 14:53:45 +0200 [thread overview]
Message-ID: <7ceba3df-bee8-9f1d-a27d-85e0b5f35d83@linaro.org> (raw)
In-Reply-To: <20230623115525.7300-1-quic_anusha@quicinc.com>
On 23/06/2023 13:55, Anusha Rao wrote:
>> Document the compatible string for ipq9574.
>>
>> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>> Reviewed-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
>> Signed-off-by: Anusha Rao <quic_anusha@quicinc.com>
>> ---
>> Changes in V4:
>> - Picked up Reviewed-by tag.
>
> A gentle reminder to pick the dt-binding patch.
> As the dts change is picked, this patch is required to resolve dt-bindings check issues.
One patchset with four patches targeting three different subsystems, so
no wonder it gets missed. You will usually receive better results with
splitting such patchsets per subsystems.
One more thing is lack of proper subject prefix which indicates the
subsystem. Without it why anyone would pick it up? For example me, I
would just ignore it for my subsystem...
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-23 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 16:11 [PATCH V4 0/4] Enable crypto for ipq9574 Anusha Rao
2023-05-26 16:11 ` [PATCH V4 1/4] dt-bindings: clock: Add crypto clock and reset definitions Anusha Rao
2023-05-26 16:11 ` [PATCH V4 2/4] clk: qcom: gcc-ipq9574: Enable crypto clocks Anusha Rao
2023-05-26 16:11 ` [PATCH V4 3/4] dt-bindings: qcom-qce: add SoC compatible string for ipq9574 Anusha Rao
2023-06-23 11:55 ` Anusha Rao
2023-06-23 12:53 ` Krzysztof Kozlowski [this message]
2023-07-12 6:30 ` Anusha Canchi
2023-05-26 16:11 ` [PATCH V4 4/4] arm64: dts: qcom: ipq9574: Enable crypto nodes Anusha Rao
2023-06-13 22:30 ` (subset) [PATCH V4 0/4] Enable crypto for ipq9574 Bjorn Andersson
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=7ceba3df-bee8-9f1d-a27d-85e0b5f35d83@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.sharma@linaro.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=quic_anusha@quicinc.com \
--cc=quic_arajkuma@quicinc.com \
--cc=quic_gokulsri@quicinc.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_poovendh@quicinc.com \
--cc=quic_sjaganat@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=thara.gopinath@gmail.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