[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1610181323370.20737@linuxheads99>
Date: Tue, 18 Oct 2016 13:28:08 -0500
From: atull <atull@...nsource.altera.com>
To: Moritz Fischer <moritz.fischer@...us.com>
CC: Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Mark Rutland <mark.rutland@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Jon Masters <jcm@...hat.com>,
Michal Simek <michal.simek@...inx.com>,
Jonathan Corbet <corbet@....net>,
Cyril Chemparathy <cyril.chemparathy@...inx.com>,
Matthew Gerlach <mgerlach@...nsource.altera.com>,
Dinh Nguyen <dinguyen@...nsource.altera.com>,
Devicetree List <devicetree@...r.kernel.org>,
<linux-doc@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Alan Tull <delicious.quinoa@...il.com>
Subject: Re: [PATCH v20 02/10] doc: fpga-mgr: add fpga image info to api
On Mon, 17 Oct 2016, Moritz Fischer wrote:
> Hi Alan,
>
> couple of nits inline and some comments on ordering the patches ;-)
>
> On Mon, Oct 17, 2016 at 6:09 PM, Alan Tull <atull@...nsource.altera.com> wrote:
> > This patch adds a minor change in the FPGA Mangager API
>
> s/Mangager/Manager/
Yup!
>
> > to hold information that is specific to an FPGA image
> > file. This change is expected to bring little, if any,
> > pain.
> >
> > An FPGA image file will have particulars that affect how the
> > image is programmed to the FPGA. One example is that
> > current 'flags' currently has one bit which shows whether the
> > FPGA image was built for full reconfiguration or partial
> > reconfiguration. Another example is timeout values for
> > enabling or disabling the bridges in the FPGA. As the
> > complexity of the FPGA design increases, the bridges in the
> > FPGA may take longer times to enable or disable.
>
> According for the current ordering bridges are not yet defined if we
> merge patches in this order?
> Not terrible imho, but I thought I'd point it out. Would swapping the
> order make sense?
Probably, yes.
>
> I also think [5/10] should be squashed together with this commit to
> make it an atomic change.
So far my bindings and code have gone in separately.
Bindings through Rob and code through Greg KH or Dinh.
>
> Apart from my comments above feel free to add my Acked-by
>
> Thanks for keeping this going,
>
> Moritz
>
Thanks for all the code reviews!
Alan
Powered by blists - more mailing lists