From: Rob Herring <robh@kernel.org>
To: Nava kishore Manne <nava.manne@xilinx.com>
Cc: lakshmi.sai.krishna.potthuri@xilinx.com, michal.simek@xilinx.com,
linux-arm-kernel@lists.infradead.org, zou_wei@huawei.com,
wendy.liang@xilinx.com, gregkh@linuxfoundation.org,
iwamatsu@nigauri.org, trix@redhat.com, git@xilinx.com,
linux-kernel@vger.kernel.org, rajan.vaja@xilinx.com,
robh+dt@kernel.org, devicetree@vger.kernel.org, arnd@arndb.de,
tejas.patel@xilinx.com, chinnikishore369@gmail.com,
amit.sunil.dhamne@xilinx.com, mdf@kernel.org,
ravi.patel@xilinx.com, linux-fpga@vger.kernel.org
Subject: Re: [PATCH v8 4/5] dt-bindings: firmware: Remove xlnx,zynqmp-firmware.txt file
Date: Tue, 13 Jul 2021 16:16:20 -0600 [thread overview]
Message-ID: <20210713221620.GA944723@robh.at.kernel.org> (raw)
In-Reply-To: <20210626155248.5004-5-nava.manne@xilinx.com>
On Sat, 26 Jun 2021 21:22:47 +0530, Nava kishore Manne wrote:
> The funtionality of xlnx,zynqmp-firmware.txt is replaced with
> xlnx,zynqmp-firmware.yaml bindings so this patch removes the
> zynqmp-firmware.txt file
>
> Signed-off-by: Nava kishore Manne <nava.manne@xilinx.com>
> ---
> Changes for v8:
> -Removed xlnx,zynqmp-firmware.txt as suggested by rob.
>
> .../firmware/xilinx/xlnx,zynqmp-firmware.txt | 44 -------------------
> 1 file changed, 44 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-13 22:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 15:52 [PATCH v8 0/5]Add Bitstream configuration support for Versal Nava kishore Manne
2021-06-26 15:52 ` [PATCH v8 1/5] drivers: firmware: Add PDI load API support Nava kishore Manne
2021-07-06 21:03 ` Tom Rix
2021-07-08 11:40 ` Nava kishore Manne
2021-06-26 15:52 ` [PATCH v8 2/5] dt-bindings: fpga: Add binding doc for versal fpga manager Nava kishore Manne
2021-06-26 15:52 ` [PATCH v8 3/5] dt-bindings: firmware: Add bindings for xilinx firmware Nava kishore Manne
2021-07-13 22:15 ` Rob Herring
2021-06-26 15:52 ` [PATCH v8 4/5] dt-bindings: firmware: Remove xlnx, zynqmp-firmware.txt file Nava kishore Manne
2021-07-06 21:09 ` [PATCH v8 4/5] dt-bindings: firmware: Remove xlnx,zynqmp-firmware.txt file Tom Rix
2021-07-08 11:42 ` Nava kishore Manne
2021-07-13 22:16 ` Rob Herring [this message]
2021-06-26 15:52 ` [PATCH v8 5/5] fpga: versal-fpga: Add versal fpga manager driver Nava kishore Manne
2021-07-06 21:34 ` Tom Rix
2021-07-08 11:57 ` 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=20210713221620.GA944723@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=amit.sunil.dhamne@xilinx.com \
--cc=arnd@arndb.de \
--cc=chinnikishore369@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=iwamatsu@nigauri.org \
--cc=lakshmi.sai.krishna.potthuri@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=nava.manne@xilinx.com \
--cc=rajan.vaja@xilinx.com \
--cc=ravi.patel@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=tejas.patel@xilinx.com \
--cc=trix@redhat.com \
--cc=wendy.liang@xilinx.com \
--cc=zou_wei@huawei.com \
/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).