All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Nava kishore Manne <nava.manne@xilinx.com>
Cc: mark.rutland@arm.com, michal.simek@xilinx.com, atull@kernel.org,
	mdf@kernel.org, jollys@xilinx.com, sboyd@kernel.org,
	rajanv@xilinx.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org,
	chinnikishore369@gmail.com
Subject: Re: [RFC PATCH v2 2/3] dt-bindings: fpga: Add bindings for ZynqMP fpga driver
Date: Tue, 25 Sep 2018 15:17:20 -0500	[thread overview]
Message-ID: <20180925201720.GA32354@bogus> (raw)
In-Reply-To: <20180905072448.12488-3-nava.manne@xilinx.com>

On Wed, Sep 05, 2018 at 12:54:47PM +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 v2:
>                 -Moved pcap node as a child to firwmare
>                  node as suggested by Rob.

Sorry, but I wasn't thinking that you already have a node defined under 
/firmware. There's no reason to have this pcap node as a child of it. 
The existing node can instantiate multiple providers including this and 
reset provider.

>  .../firmware/xilinx/xlnx,zynqmp-firmware.txt        | 13 +++++++++++++
>  1 file changed, 13 insertions(+)

WARNING: multiple messages have this Message-ID (diff)
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 2/3] dt-bindings: fpga: Add bindings for ZynqMP fpga driver
Date: Tue, 25 Sep 2018 15:17:20 -0500	[thread overview]
Message-ID: <20180925201720.GA32354@bogus> (raw)
In-Reply-To: <20180905072448.12488-3-nava.manne@xilinx.com>

On Wed, Sep 05, 2018 at 12:54:47PM +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 v2:
>                 -Moved pcap node as a child to firwmare
>                  node as suggested by Rob.

Sorry, but I wasn't thinking that you already have a node defined under 
/firmware. There's no reason to have this pcap node as a child of it. 
The existing node can instantiate multiple providers including this and 
reset provider.

>  .../firmware/xilinx/xlnx,zynqmp-firmware.txt        | 13 +++++++++++++
>  1 file changed, 13 insertions(+)

  reply	other threads:[~2018-09-25 20:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04  7:23 [RFC PATCH v2 0/3] Add Bitstream configuration support for ZynqMP Nava kishore Manne
2018-09-05  7:24 ` Nava kishore Manne
2018-09-05  7:24 ` Nava kishore Manne
2018-09-05  7:24 ` Nava kishore Manne
2018-09-04  7:23 ` [RFC PATCH v2 1/3] firmware: xilinx: Add fpga API's Nava kishore Manne
2018-09-05  7:24   ` Nava kishore Manne
2018-09-05  7:24   ` Nava kishore Manne
2018-09-05  7:24   ` Nava kishore Manne
2018-09-04  7:23 ` [RFC PATCH v2 2/3] dt-bindings: fpga: Add bindings for ZynqMP fpga driver Nava kishore Manne
2018-09-05  7:24   ` Nava kishore Manne
2018-09-05  7:24   ` Nava kishore Manne
2018-09-05  7:24   ` Nava kishore Manne
2018-09-25 20:17   ` Rob Herring [this message]
2018-09-25 20:17     ` Rob Herring
2018-09-04  7:24 ` Nava kishore Manne
2018-09-05  7:24 ` [RFC PATCH v2 3/3] fpga manager: Adding FPGA Manager support for Xilinx zynqmp Nava kishore Manne
2018-09-05  7:24   ` Nava kishore Manne
2018-09-05  7:24   ` Nava kishore Manne

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=20180925201720.GA32354@bogus \
    --to=robh@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=mdf@kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=nava.manne@xilinx.com \
    --cc=rajanv@xilinx.com \
    --cc=sboyd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.