From: Moritz Fischer <mdf@kernel.org>
To: Alan Tull <atull@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Nava kishore Manne <nava.manne@xilinx.com>,
Moritz Fischer <mdf@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Michal Simek <michal.simek@xilinx.com>,
Rajan Vaja <rajanv@xilinx.com>, Jolly Shah <jollys@xilinx.com>,
linux-fpga@vger.kernel.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kishore m <chinnikishore369@gmail.com>
Subject: Re: [PATCH v5 6/6] dt-bindings: fpga: Add bindings for ZynqMP fpga driver
Date: Mon, 1 Apr 2019 15:05:55 -0700 [thread overview]
Message-ID: <20190401220555.GA2716@archbook> (raw)
In-Reply-To: <CANk1AXTcwb1oJL5Uq-H-Q41-n8SXtamObSedMHSa_smZ8Xr1fw@mail.gmail.com>
On Mon, Apr 01, 2019 at 03:50:08PM -0500, Alan Tull wrote:
> On Thu, Mar 28, 2019 at 12:00 PM Rob Herring <robh@kernel.org> wrote:
> >
> > On Tue, 26 Mar 2019 20:01:29 +0530, Nava kishore Manne wrote:
> > > Add documentation to describe Xilinx ZynqMP fpga driver
> > > bindings.
> > >
> > > Signed-off-by: Nava kishore Manne <nava.manne@xilinx.com>
> > > ---
> > > Changes for v5:
> > > -Moved pcap node as a child to firwmare
> > > node as suggested by Rob.
> > > Changes for v4:
> > > -Modified binding description as suggested by Moritz Fischer.
> > > Changes for v3:
> > > -Removed PCAP as a child node to the FW and Created
> > > an independent node since PCAP driver is a consumer
> > > not a provider.
> > >
> > > .../bindings/fpga/xlnx,zynqmp-pcap-fpga.txt | 25 +++++++++++++++++++
> > > 1 file changed, 25 insertions(+)
> > > create mode 100644 Documentation/devicetree/bindings/fpga/xlnx,zynqmp-pcap-fpga.txt
> > >
> >
> > Reviewed-by: Rob Herring <robh@kernel.org>
>
> Acked-by: Alan Tull <atull@kernel.org>
Acked-by: Moritz Fischer <mdf@kernel.org>
prev parent reply other threads:[~2019-04-01 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 14:31 [PATCH v5 0/6]dt-bindings: Firmware node binding for ZynqMP core Nava kishore Manne
2019-03-26 14:31 ` [PATCH v5 1/6] dt-bindings: power: Add ZynqMP power domain bindings Nava kishore Manne
2019-03-26 14:31 ` [PATCH v5 2/6] dt-bindings: soc: Add ZynqMP PM bindings Nava kishore Manne
2019-03-26 14:31 ` [PATCH v5 3/6] dt-bindings: reset: Add bindings for ZynqMP reset driver Nava kishore Manne
2019-03-26 14:31 ` [PATCH v5 4/6] dt-bindings: pinctrl: Add ZynqMP pin controller bindings Nava kishore Manne
2019-03-26 14:31 ` [PATCH v5 5/6] dt-bindings: nvmem: Add bindings for ZynqMP nvmem driver Nava kishore Manne
2019-03-26 14:31 ` [PATCH v5 6/6] dt-bindings: fpga: Add bindings for ZynqMP fpga driver Nava kishore Manne
2019-03-28 17:00 ` Rob Herring
2019-04-01 20:50 ` Alan Tull
2019-04-01 22:05 ` Moritz Fischer [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=20190401220555.GA2716@archbook \
--to=mdf@kernel.org \
--cc=atull@kernel.org \
--cc=chinnikishore369@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jollys@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=nava.manne@xilinx.com \
--cc=rajanv@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=robh@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).