From: Ang, Chee Hong <chee.hong.ang@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v6 0/4] Stratix10 FPGA reconfiguration support
Date: Wed, 19 Dec 2018 04:53:23 +0000 [thread overview]
Message-ID: <1545195202.78705.3.camel@intel.com> (raw)
In-Reply-To: <8bc31750-fd4d-37e7-858f-42675e732739@denx.de>
On Tue, 2018-12-18 at 18:47 +0100, Marek Vasut wrote:
> On 12/18/2018 09:54 AM, chee.hong.ang at intel.com wrote:
> >
> > From: "Ang, Chee Hong" <chee.hong.ang@intel.com>
> >
> > Summary of v6 changes:
> > - Patch 1/4 and 4/4 are unchanged
> > - Patch 2/4:
> > - fixed compilation warnings in drivers/fpga/stratix10.c
> > - Patch 3/4:
> > - socfpga_fpga_add() in misc.c
> > - define fpga descriptor structure in misc_arria10.c, misc_gen5.c
> > &
> > misc_s10.c respectively
> > - removed for-loop in socfpga_fpga_add() (only 1 FPGA device
> > added)
> >
> > v5 patchsets:
> > https://lists.denx.de/pipermail/u-boot/2018-November/349670.html
> >
> > Ang, Chee Hong (4):
> > arm: socfpga: stratix10: Add macros for mailbox's arguments
> > arm: socfpga: stratix10: Add Stratix 10 FPGA Reconfiguration
> > Driver
> > arm: socfpga: stratix10: Add Stratix10 FPGA into FPGA device
> > table
> > arm: socfpga: stratix10: Enable Stratix10 FPGA Reconfiguration
> >
> > arch/arm/mach-socfpga/include/mach/mailbox_s10.h | 6 +
> > arch/arm/mach-socfpga/include/mach/misc.h | 4 +-
> > arch/arm/mach-socfpga/misc.c | 26 +-
> > arch/arm/mach-socfpga/misc_arria10.c | 22 +-
> > arch/arm/mach-socfpga/misc_gen5.c | 22 +-
> > arch/arm/mach-socfpga/misc_s10.c | 22 ++
> > configs/socfpga_stratix10_defconfig | 1 +
> > drivers/fpga/Kconfig | 11 +
> > drivers/fpga/Makefile | 1 +
> > drivers/fpga/altera.c | 6 +
> > drivers/fpga/stratix10.c | 288
> > +++++++++++++++++++++++
> > include/altera.h | 8 +
> > 12 files changed, 389 insertions(+), 28 deletions(-)
> > create mode 100644 drivers/fpga/stratix10.c
> I take it this fixes the previous stratix 10 build breakage, right ?
> let's see what travis says.
Yes. Actually they are just compilation warnings to me. Your travis's
build settings treat all warning as error. Please let me know about the
travis report. Thanks.
>
next prev parent reply other threads:[~2018-12-19 4:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 8:54 [U-Boot] [PATCH v6 0/4] Stratix10 FPGA reconfiguration support chee.hong.ang at intel.com
2018-12-18 8:54 ` [U-Boot] [PATCH v6 1/4] arm: socfpga: stratix10: Add macros for mailbox's arguments chee.hong.ang at intel.com
2018-12-18 8:54 ` [U-Boot] [PATCH v6 2/4] arm: socfpga: stratix10: Add Stratix 10 FPGA Reconfiguration Driver chee.hong.ang at intel.com
2018-12-18 8:54 ` [U-Boot] [PATCH v6 3/4] arm: socfpga: stratix10: Add Stratix10 FPGA into FPGA device table chee.hong.ang at intel.com
2018-12-18 8:54 ` [U-Boot] [PATCH v6 4/4] arm: socfpga: stratix10: Enable Stratix10 FPGA Reconfiguration chee.hong.ang at intel.com
2018-12-18 17:47 ` Marek Vasut
2018-12-19 4:55 ` Ang, Chee Hong
2018-12-19 8:41 ` Marek Vasut
2018-12-19 9:48 ` Ang, Chee Hong
2018-12-19 10:07 ` Marek Vasut
2018-12-18 17:47 ` [U-Boot] [PATCH v6 0/4] Stratix10 FPGA reconfiguration support Marek Vasut
2018-12-19 4:53 ` Ang, Chee Hong [this message]
2018-12-19 8:18 ` Marek Vasut
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=1545195202.78705.3.camel@intel.com \
--to=chee.hong.ang@intel.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