Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935272AbcJQVA2 (ORCPT ); Mon, 17 Oct 2016 17:00:28 -0400 Received: from mail-vk0-f41.google.com ([209.85.213.41]:36728 "EHLO mail-vk0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933244AbcJQVAV (ORCPT ); Mon, 17 Oct 2016 17:00:21 -0400 MIME-Version: 1.0 In-Reply-To: <20161017160941.4205-3-atull@opensource.altera.com> References: <20161017160941.4205-1-atull@opensource.altera.com> <20161017160941.4205-3-atull@opensource.altera.com> From: Moritz Fischer Date: Mon, 17 Oct 2016 23:00:19 +0200 Message-ID: Subject: Re: [PATCH v20 02/10] doc: fpga-mgr: add fpga image info to api To: Alan Tull Cc: Rob Herring , Frank Rowand , Mark Rutland , Greg Kroah-Hartman , Ian Campbell , Jon Masters , Michal Simek , Jonathan Corbet , Cyril Chemparathy , Matthew Gerlach , Dinh Nguyen , Devicetree List , linux-doc@vger.kernel.org, linux-arm-kernel , Linux Kernel Mailing List , Alan Tull Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1214 Lines: 35 Hi Alan, couple of nits inline and some comments on ordering the patches ;-) On Mon, Oct 17, 2016 at 6:09 PM, Alan Tull wrote: > This patch adds a minor change in the FPGA Mangager API s/Mangager/Manager/ > 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? I also think [5/10] should be squashed together with this commit to make it an atomic change. Apart from my comments above feel free to add my Acked-by Thanks for keeping this going, Moritz