linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: trix@redhat.com, mdf@kernel.org, hao.wu@intel.com,
	michal.simek@xilinx.com, gregkh@linuxfoundation.org,
	krzysztof.kozlowski@canonical.com, dinguyen@kernel.org,
	nava.manne@xilinx.com, yilun.xu@intel.com, davidgow@google.com,
	fpacheco@redhat.com, richard.gong@intel.com
Cc: linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/4] fpga: dfl: reorganize to subdir layout
Date: Mon, 14 Jun 2021 11:28:41 +0200	[thread overview]
Message-ID: <3e83dee8-4746-b22b-c032-1d73364f9cb7@lucaceresoli.net> (raw)
In-Reply-To: <20210611162129.3203483-3-trix@redhat.com>

Hi Tom,

On 11/06/21 18:21, trix@redhat.com wrote:
> From: Tom Rix <trix@redhat.com>
> 
> Follow drivers/net/ethernet/ which has control configs
> NET_VENDOR_BLA that map to drivers/net/ethernet/bla
> Since fpgas do not have many vendors, drop the 'VENDOR' and use
> FPGA_BLA.
> 
> There are several new subdirs
> altera/
> dfl/
> lattice/
> xilinx/
> 
> Each subdir has a Kconfig that has a new/reused
> 
> if FPGA_BLA
>   ... existing configs ...
> endif FPGA_BLA
> 
> Which is sourced into the main fpga/Kconfig
> 
> Each subdir has a Makefile whose transversal is controlled in the
> fpga/Makefile by
> 
> obj-$(CONFIG_FPGA_BLA) += bla/
> 
> This is the dfl/ subdir part.
> 
> Create a dfl/ subdir
> Move dfl-* files to it.
> Add a Kconfig and Makefile
> 
> Because FPGA_DFL is now used in dfl/Kconfig in a if/endif
> block, all the other configs in dfl/Kconfig implicitly depend
> on FPGA_DFL.  So the explicit dependence can be removed.  Also
> since FPGA_DFL depends on HAS_IOMEM, it can be removed from the
> other configs.
> 
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
>  MAINTAINERS                                 |  2 +-
>  drivers/fpga/Kconfig                        | 80 +-------------------
>  drivers/fpga/Makefile                       | 18 +----
>  drivers/fpga/dfl/Kconfig                    | 83 +++++++++++++++++++++
>  drivers/fpga/dfl/Makefile                   | 16 ++++
>  drivers/fpga/{ => dfl}/dfl-afu-dma-region.c |  0
>  drivers/fpga/{ => dfl}/dfl-afu-error.c      |  0
>  drivers/fpga/{ => dfl}/dfl-afu-main.c       |  0
>  drivers/fpga/{ => dfl}/dfl-afu-region.c     |  0
>  drivers/fpga/{ => dfl}/dfl-afu.h            |  0
>  drivers/fpga/{ => dfl}/dfl-fme-br.c         |  0
>  drivers/fpga/{ => dfl}/dfl-fme-error.c      |  0
>  drivers/fpga/{ => dfl}/dfl-fme-main.c       |  0
>  drivers/fpga/{ => dfl}/dfl-fme-mgr.c        |  0
>  drivers/fpga/{ => dfl}/dfl-fme-perf.c       |  0
>  drivers/fpga/{ => dfl}/dfl-fme-pr.c         |  0
>  drivers/fpga/{ => dfl}/dfl-fme-pr.h         |  0
>  drivers/fpga/{ => dfl}/dfl-fme-region.c     |  0
>  drivers/fpga/{ => dfl}/dfl-fme.h            |  0
>  drivers/fpga/{ => dfl}/dfl-n3000-nios.c     |  0
>  drivers/fpga/{ => dfl}/dfl-pci.c            |  0
>  drivers/fpga/{ => dfl}/dfl.c                |  0
>  drivers/fpga/{ => dfl}/dfl.h                |  0
>  23 files changed, 102 insertions(+), 97 deletions(-)
>  create mode 100644 drivers/fpga/dfl/Kconfig
>  create mode 100644 drivers/fpga/dfl/Makefile
>  rename drivers/fpga/{ => dfl}/dfl-afu-dma-region.c (100%)
>  rename drivers/fpga/{ => dfl}/dfl-afu-error.c (100%)
>  rename drivers/fpga/{ => dfl}/dfl-afu-main.c (100%)
>  rename drivers/fpga/{ => dfl}/dfl-afu-region.c (100%)
>  rename drivers/fpga/{ => dfl}/dfl-afu.h (100%)
>  rename drivers/fpga/{ => dfl}/dfl-fme-br.c (100%)
>  rename drivers/fpga/{ => dfl}/dfl-fme-error.c (100%)
>  rename drivers/fpga/{ => dfl}/dfl-fme-main.c (100%)
>  rename drivers/fpga/{ => dfl}/dfl-fme-mgr.c (100%)
>  rename drivers/fpga/{ => dfl}/dfl-fme-perf.c (100%)
>  rename drivers/fpga/{ => dfl}/dfl-fme-pr.c (100%)

You should update Documentation/fpga/dfl.rst too as it mentions
"drivers/fpga/dfl-fme-pr.c". This update was in your initial patch 5 so
it's lost now, but it really should be in this patch.

>  rename drivers/fpga/{ => dfl}/dfl-fme-pr.h (100%)
>  rename drivers/fpga/{ => dfl}/dfl-fme-region.c (100%)
>  rename drivers/fpga/{ => dfl}/dfl-fme.h (100%)
>  rename drivers/fpga/{ => dfl}/dfl-n3000-nios.c (100%)
>  rename drivers/fpga/{ => dfl}/dfl-pci.c (100%)
>  rename drivers/fpga/{ => dfl}/dfl.c (100%)

Same as above.

-- 
Luca

  reply	other threads:[~2021-06-14  9:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 16:21 [PATCH v3 0/4] fpga: reorganize to subdirs trix
2021-06-11 16:21 ` [PATCH v3 1/4] fpga: dfl: reorganize to subdir layout trix
2021-06-14  9:28   ` Luca Ceresoli [this message]
2021-06-14 15:15     ` Tom Rix
2021-06-11 16:21 ` [PATCH v3 2/4] fpga: xilinx: " trix
2021-06-11 16:21 ` [PATCH v3 3/4] fpga: altera: " trix
2021-06-11 16:21 ` [PATCH v3 4/4] fpga: lattice: " trix

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=3e83dee8-4746-b22b-c032-1d73364f9cb7@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --cc=davidgow@google.com \
    --cc=dinguyen@kernel.org \
    --cc=fpacheco@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hao.wu@intel.com \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=nava.manne@xilinx.com \
    --cc=richard.gong@intel.com \
    --cc=trix@redhat.com \
    --cc=yilun.xu@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).