From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 6/6] fpga: xilinx: Simplify load/dump/info function handling
Date: Fri, 14 Mar 2014 16:27:07 -0400 [thread overview]
Message-ID: <20140314202707.GT16360@bill-the-cat> (raw)
In-Reply-To: <c12a663246371522f878e12c0d8a7edc15d6481d.1394722361.git.michal.simek@xilinx.com>
On Thu, Mar 13, 2014 at 03:52:48PM +0100, Michal Simek wrote:
> Connect FPGA version with appropriate operations
> to remove huge switch-cases for every FPGA family.
> Tested on Zynq. Spartan2/Spartan3/Virtex2 just compile test.
>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
I like the concept. Did you go through the u-boot.map files on
spartan/etc to make sure we aren't discarding things now? That'd be the
follow up on compile testing the series.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140314/50cdf374/attachment.pgp>
next prev parent reply other threads:[~2014-03-14 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 14:52 [U-Boot] [RFC PATCH 1/6] fpga: spartan2: Avoid CamelCase Michal Simek
2014-03-13 14:52 ` [U-Boot] [RFC PATCH 2/6] fpga: spartan3: " Michal Simek
2014-03-13 14:52 ` [U-Boot] [RFC PATCH 3/6] fpga: virtex2: " Michal Simek
2014-03-13 14:52 ` [U-Boot] [RFC PATCH 4/6] fpga: xilinx: Avoid CamelCase for in Xilinx_desc Michal Simek
2014-03-13 14:52 ` [U-Boot] [RFC PATCH 5/6] fpga: xilinx: Fix the rest of CamelCases Michal Simek
2014-03-13 14:52 ` [U-Boot] [RFC PATCH 6/6] fpga: xilinx: Simplify load/dump/info function handling Michal Simek
2014-03-14 20:27 ` Tom Rini [this message]
2014-03-17 6:27 ` 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=20140314202707.GT16360@bill-the-cat \
--to=trini@ti.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