From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 3/4] arm: zynq: fpga: Added Kconfig support for CONFIG_FPGA_ZYNQPL
Date: Wed, 28 Feb 2018 15:24:44 -0500 [thread overview]
Message-ID: <20180228202444.GK4311@bill-the-cat> (raw)
In-Reply-To: <1518784372-14228-4-git-send-email-vipulk@xilinx.com>
On Fri, Feb 16, 2018 at 06:02:51PM +0530, Vipul Kumar wrote:
> This patch added Kconfig support for CONFIG_FPGA_ZYNQPL.
>
> Signed-off-by: Vipul Kumar <vipulk@xilinx.com>
> Signed-off-by: Siva Durga Prasad Paladugu <sivadur@xilinx.com>
After merging 4/4 into this (we should always update the defconfigs in
the patch, otherwise we may get build warnings later when bisecting),
applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180228/d39c90b1/attachment.sig>
next prev parent reply other threads:[~2018-02-28 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 12:32 [U-Boot] [UBOOT PATCH 0/4] fpga: Moved fpga u-boot headers to the Kconfig Vipul Kumar
2018-02-16 12:32 ` [U-Boot] [UBOOT PATCH 1/4] fpga: Added Kconfig support for FPGA_SPARTAN3 Vipul Kumar
2018-02-28 20:24 ` [U-Boot] [U-Boot, " Tom Rini
2018-03-01 7:05 ` Michal Simek
2018-03-01 14:28 ` Tom Rini
2018-03-01 14:30 ` Michal Simek
2018-02-16 12:32 ` [U-Boot] [UBOOT PATCH 2/4] fpga: Added CONFIG_FPGA_SPARTAN3 in the the respective defconfig Vipul Kumar
2018-02-16 12:32 ` [U-Boot] [UBOOT PATCH 3/4] arm: zynq: fpga: Added Kconfig support for CONFIG_FPGA_ZYNQPL Vipul Kumar
2018-02-28 20:24 ` Tom Rini [this message]
2018-02-16 12:32 ` [U-Boot] [UBOOT PATCH 4/4] arm: zynq: fpga: Added CONFIG_FPGA_ZYNQPL in the respective defconfig Vipul Kumar
2018-02-26 9:41 ` [U-Boot] [UBOOT PATCH 0/4] fpga: Moved fpga u-boot headers to the Kconfig Michal Simek
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=20180228202444.GK4311@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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