public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Xu Yilun <yilun.xu@intel.com>
Cc: mdf@kernel.org, krzk@kernel.org, linux-fpga@vger.kernel.org,
	linux-kernel@vger.kernel.org, trix@redhat.com,
	lgoncalv@redhat.com, hao.wu@intel.com
Subject: Re: [PATCH v9 4/6] fpga: dfl: move dfl bus related APIs to include/linux/fpga/dfl.h
Date: Sun, 11 Oct 2020 16:45:22 +0200	[thread overview]
Message-ID: <20201011144522.GB271501@kroah.com> (raw)
In-Reply-To: <1602313793-21421-5-git-send-email-yilun.xu@intel.com>

On Sat, Oct 10, 2020 at 03:09:51PM +0800, Xu Yilun wrote:
> Now the dfl drivers could be made as independent modules and put in
> different folders according to their functionalities. In order for
> scattered dfl device drivers to include dfl bus APIs, move the
> dfl bus APIs to a new header file in the public folder.
> 
> [mdf@kernel.org: Fixed up MAINTAINERS entry merge]
> Signed-off-by: Xu Yilun <yilun.xu@intel.com>
> Reviewed-by: Tom Rix <trix@redhat.com>
> Acked-by: Wu Hao <hao.wu@intel.com>
> Signed-off-by: Moritz Fischer <mdf@kernel.org>
> ---
> v2: updated the MAINTAINERS under FPGA DFL DRIVERS
>     improve the comments
>     rename the dfl-bus.h to dfl.h
> v3: rebase the patch for previous changes
> v9: rebase the patch for bus name changes back to "dfl"
> ---
>  MAINTAINERS              |  1 +
>  drivers/fpga/dfl.c       |  1 +
>  drivers/fpga/dfl.h       | 72 ----------------------------------------
>  include/linux/fpga/dfl.h | 86 ++++++++++++++++++++++++++++++++++++++++++++++++

Why in the fpga directory?

thanks,

greg k-h

  reply	other threads:[~2020-10-11 14:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-10  7:09 [PATCH v9 0/6] add DFL bus support to MODULE_DEVICE_TABLE() Xu Yilun
2020-10-10  7:09 ` [PATCH v9 1/6] fpga: dfl: fix the definitions of type & feature_id for dfl devices Xu Yilun
2020-10-10 15:07   ` Tom Rix
2020-10-12  2:41     ` Xu Yilun
2020-10-12 14:07       ` Tom Rix
2020-10-12 14:32         ` Greg KH
2020-10-10  7:09 ` [PATCH v9 2/6] fpga: dfl: move dfl_device_id to mod_devicetable.h Xu Yilun
2020-10-11 14:43   ` Greg KH
2020-10-12  2:27     ` Xu Yilun
2020-10-10  7:09 ` [PATCH v9 3/6] fpga: dfl: add dfl bus support to MODULE_DEVICE_TABLE() Xu Yilun
2020-10-10  7:09 ` [PATCH v9 4/6] fpga: dfl: move dfl bus related APIs to include/linux/fpga/dfl.h Xu Yilun
2020-10-11 14:45   ` Greg KH [this message]
2020-10-12  2:31     ` Xu Yilun
2020-10-10  7:09 ` [PATCH v9 5/6] fpga: dfl: add support for N3000 Nios private feature Xu Yilun
2020-10-10 21:21   ` Tom Rix
2020-10-12  6:51     ` Xu Yilun
2020-10-12 14:19       ` Tom Rix
2020-10-10  7:09 ` [PATCH v9 6/6] memory: dfl-emif: add the DFL EMIF private feature driver Xu Yilun
2020-10-12 16:40   ` Krzysztof Kozlowski
2020-10-12 16:58     ` Moritz Fischer
2020-10-12 17:27       ` Krzysztof Kozlowski

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=20201011144522.GB271501@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=hao.wu@intel.com \
    --cc=krzk@kernel.org \
    --cc=lgoncalv@redhat.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --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