From: Rob Herring <robh@kernel.org>
Cc: swboyd@chromium.org, dianders@chromium.org, broonie@kernel.org,
mka@chromium.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
devicetree@vger.kernel.org, Dilip Kota <dkota@codeaurora.org>
Subject: Re: [PATCH V4 2/4] dt-bindings: soc: qcom: GENI SE SPI controller device tree binding
Date: Wed, 26 Sep 2018 17:51:20 -0500 [thread overview]
Message-ID: <20180926225120.GA14357@bogus> (raw)
In-Reply-To: <1537294047-12093-3-git-send-email-dkota@codeaurora.org>
On Tue, 18 Sep 2018 23:37:24 +0530, Dilip Kota wrote:
> Move GENI SE SPI controller device-tree bindings
> from devicetree/bindings/soc/qcom/qcom,geni-se.txt
> to devicetree/bindings/spi/qcom,spi-geni-qcom.txt.
>
> Signed-off-by: Dilip Kota <dkota@codeaurora.org>
> ---
> .../devicetree/bindings/soc/qcom/qcom,geni-se.txt | 27 ++-------------
> .../devicetree/bindings/spi/qcom,spi-geni-qcom.txt | 39 ++++++++++++++++++++++
> 2 files changed, 41 insertions(+), 25 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/spi/qcom,spi-geni-qcom.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2018-09-26 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1537294047-12093-1-git-send-email-dkota@codeaurora.org>
2018-09-18 18:07 ` [PATCH V4 1/4] dt-bindings: soc: qcom: Remove SPI controller maximum frequency binding Dilip Kota
2018-09-18 20:11 ` Doug Anderson
2018-09-20 15:38 ` Stephen Boyd
2018-09-26 22:51 ` Rob Herring
2018-09-18 18:07 ` [PATCH V4 2/4] dt-bindings: soc: qcom: GENI SE SPI controller device tree binding Dilip Kota
2018-09-18 20:11 ` Doug Anderson
2018-09-20 15:39 ` Stephen Boyd
2018-09-26 22:51 ` Rob Herring [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=20180926225120.GA14357@bogus \
--to=robh@kernel.org \
--cc=andy.gross@linaro.org \
--cc=broonie@kernel.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dkota@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=swboyd@chromium.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).