Linux Remote Processor Subsystem development
 help / color / mirror / Atom feed
From: "Sireesh Kodali" <sireeshkodali1@gmail.com>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	<devicetree@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
	<linux-remoteproc@vger.kernel.org>
Cc: <bjorn.andersson@linaro.org>, "Andy Gross" <agross@kernel.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: msm8916: Fix typo in pronto remoteproc node
Date: Thu, 12 May 2022 15:07:32 +0530	[thread overview]
Message-ID: <CJXOKK6WT06F.109YU66ZCBP5T@skynet-linux> (raw)
In-Reply-To: <81365629-6cf0-f320-e684-4fb40b829399@linaro.org>

On Wed May 11, 2022 at 11:41 PM IST, Krzysztof Kozlowski wrote:
> On 10/05/2022 06:26, Sireesh Kodali wrote:
> > The smem-state properties for the pronto node were incorrectly labelled,
> > reading `qcom,state*` rather than `qcom,smem-state*`. Fix that, allowing
> > the stop state to be used.
> > 
> > Fixes: 88106096cbf8 ("ARM: dts: msm8916: Add and enable wcnss node")
> > 
> > Signed-off-by: Sireesh Kodali <sireeshkodali1@gmail.com>
>
> No blank lines between tags, please.
>
> Best regards,
> Krzysztof

Will fix in v2

Thanks,
Sireesh

      reply	other threads:[~2022-05-12  9:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10  4:26 [PATCH 0/2] remoteproc: qcom: Fix handling of WCNSS IRQs Sireesh Kodali
2022-05-10  4:26 ` [PATCH 1/2] remoteproc: qcom: wcnss: Fix handling of IRQs Sireesh Kodali
2022-05-10  4:26 ` [PATCH 2/2] arm64: dts: qcom: msm8916: Fix typo in pronto remoteproc node Sireesh Kodali
2022-05-11 17:51   ` Stephan Gerhold
2022-05-11 18:11   ` Krzysztof Kozlowski
2022-05-12  9:37     ` Sireesh Kodali [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=CJXOKK6WT06F.109YU66ZCBP5T@skynet-linux \
    --to=sireeshkodali1@gmail.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=robh+dt@kernel.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