From: Michal Simek <michal.simek@xilinx.com>
To: Jolly Shah <jolly.shah@xilinx.com>, <robh+dt@kernel.org>
Cc: <michal.simek@xilinx.com>, <rajanv@xilinx.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
Jolly Shah <jollys@xilinx.com>
Subject: Re: [PATCH 0/2] Rename dt header and move clock binding
Date: Mon, 18 Mar 2019 13:42:05 +0100 [thread overview]
Message-ID: <a23b7c49-d6fb-5e11-7770-c860e8c9b8f9@xilinx.com> (raw)
In-Reply-To: <1551300670-6949-1-git-send-email-jollys@xilinx.com>
On 27. 02. 19 21:51, Jolly Shah wrote:
> This patchset renames clock dt include file to align with other incldues.
> Other patch moves clock binding to a separate file under clock directory to
> align with other firmware child binding documenetation.
>
> Jolly Shah (1):
> include: dt-binding: clock: Rename zynqmp header file
>
> Rajan Vaja (1):
> dt-bindings: xilinx: Separate clock binding from firmware doc
>
> .../devicetree/bindings/clock/xlnx,zynqmp-clk.txt | 63 +++++++++++
> .../firmware/xilinx/xlnx,zynqmp-firmware.txt | 54 +--------
> include/dt-bindings/clock/xlnx,zynqmp-clk.h | 116 -------------------
> include/dt-bindings/clock/xlnx-zynqmp-clk.h | 126 +++++++++++++++++++++
> 4 files changed, 190 insertions(+), 169 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/clock/xlnx,zynqmp-clk.txt
> delete mode 100644 include/dt-bindings/clock/xlnx,zynqmp-clk.h
> create mode 100644 include/dt-bindings/clock/xlnx-zynqmp-clk.h
>
I have applied this. Please let me know if you see any issue with it.
Thanks,
Michal
prev parent reply other threads:[~2019-03-18 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 20:51 [PATCH 0/2] Rename dt header and move clock binding Jolly Shah
2019-02-27 20:51 ` [PATCH 1/2] include: dt-binding: clock: Rename zynqmp header file Jolly Shah
2019-02-27 20:51 ` [PATCH 2/2] dt-bindings: xilinx: Separate clock binding from firmware doc Jolly Shah
2019-03-18 12:42 ` Michal Simek [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=a23b7c49-d6fb-5e11-7770-c860e8c9b8f9@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=jolly.shah@xilinx.com \
--cc=jollys@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rajanv@xilinx.com \
--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;
as well as URLs for NNTP newsgroup(s).