From: Rob Herring <robh@kernel.org>
To: Gokul Sriram Palanisamy <gokulsri@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, robh+dt@kernel.org,
sboyd@kernel.org, agross@kernel.org, jassisinghbrar@gmail.com,
bjorn.andersson@linaro.org, mturquette@baylibre.com,
mark.rutland@arm.com, sricharan@codeaurora.org,
devicetree@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org, david.brown@linaro.org,
linux-clk@vger.kernel.org, ohad@wizery.com
Subject: Re: [PATCH 1/3] dt-bindings: remoteproc: qcom: Add Q6V5 Modem PIL binding for IPQ6018
Date: Tue, 9 Feb 2021 14:05:20 -0600 [thread overview]
Message-ID: <20210209200520.GA75242@robh.at.kernel.org> (raw)
In-Reply-To: <1611940320-24830-2-git-send-email-gokulsri@codeaurora.org>
On Fri, 29 Jan 2021 22:41:58 +0530, Gokul Sriram Palanisamy wrote:
> Add a new modem compatible string for IPQ6018 SoCs
>
> Signed-off-by: Gokul Sriram Palanisamy <gokulsri@codeaurora.org>
> ---
> Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-02-09 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 17:11 [PATCH 0/3] remoteproc: qcom: q6v5-wcss: Add driver data for IPQ6018 Gokul Sriram Palanisamy
2021-01-29 17:11 ` [PATCH 1/3] dt-bindings: remoteproc: qcom: Add Q6V5 Modem PIL binding " Gokul Sriram Palanisamy
2021-02-09 20:05 ` Rob Herring [this message]
2021-01-29 17:11 ` [PATCH 2/3] remoteproc: qcom: wcss: populate driver data " Gokul Sriram Palanisamy
2021-03-18 2:10 ` Bjorn Andersson
2021-01-29 17:12 ` [PATCH 3/3] arm64: dts: ipq6018: Update WCSS PIL driver compatible Gokul Sriram Palanisamy
-- strict thread matches above, loose matches on Subject: below --
2021-01-29 17:09 [PATCH 0/3] remoteproc: qcom: q6v5-wcss: Add driver data for IPQ6018 Gokul Sriram Palanisamy
2021-01-29 17:09 ` [PATCH 1/3] dt-bindings: remoteproc: qcom: Add Q6V5 Modem PIL binding " Gokul Sriram Palanisamy
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=20210209200520.GA75242@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gokulsri@codeaurora.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sricharan@codeaurora.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).