linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Moritz Fischer <mdf@kernel.org>
To: Wu Hao <hao.wu@intel.com>
Cc: mdf@kernel.org, linux-fpga@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
	yilun.xu@intel.com, gregkh@linuxfoundation.org, atull@kernel.org
Subject: Re: [PATCH v4 05/15] Documentation: fpga: dfl: add descriptions for virtualization and new interfaces.
Date: Thu, 27 Jun 2019 18:12:56 -0700	[thread overview]
Message-ID: <20190628011256.GB5671@archbook> (raw)
In-Reply-To: <1561610695-5414-6-git-send-email-hao.wu@intel.com>

Hi Wu,

On Thu, Jun 27, 2019 at 12:44:45PM +0800, Wu Hao wrote:
> This patch adds virtualization support description for DFL based
> FPGA devices (based on PCIe SRIOV), and introductions to new
> interfaces added by new dfl private feature drivers.
> 
> Signed-off-by: Xu Yilun <yilun.xu@intel.com>
> Signed-off-by: Wu Hao <hao.wu@intel.com>
> Acked-by: Alan Tull <atull@kernel.org>
> ---
>  Documentation/fpga/dfl.txt | 101 +++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 101 insertions(+)
> 
> diff --git a/Documentation/fpga/dfl.txt b/Documentation/fpga/dfl.txt
> index 6df4621..a22631f 100644
> --- a/Documentation/fpga/dfl.txt
> +++ b/Documentation/fpga/dfl.txt

This got re{named,formatted} in linux-next. I've tried to fix it before sending it
to Greg.

Thanks,
Moritz

  reply	other threads:[~2019-06-28  1:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27  4:44 [PATCH v4 00/15] add new features for FPGA DFL drivers Wu Hao
2019-06-27  4:44 ` [PATCH v4 01/15] fpga: dfl-fme-mgr: fix FME_PR_INTFC_ID register address Wu Hao
2019-06-27  4:44 ` [PATCH v4 02/15] fpga: dfl: fme: remove copy_to_user() in ioctl for PR Wu Hao
2019-06-27  4:44 ` [PATCH v4 03/15] fpga: dfl: fme: align PR buffer size per PR datawidth Wu Hao
2019-06-27  4:44 ` [PATCH v4 04/15] fpga: dfl: fme: support 512bit data width PR Wu Hao
2019-06-27  4:44 ` [PATCH v4 05/15] Documentation: fpga: dfl: add descriptions for virtualization and new interfaces Wu Hao
2019-06-28  1:12   ` Moritz Fischer [this message]
2019-06-28  2:13     ` Wu Hao
2019-07-01  6:30       ` Wu Hao
2019-06-27  4:44 ` [PATCH v4 06/15] fpga: dfl: fme: add DFL_FPGA_FME_PORT_RELEASE/ASSIGN ioctl support Wu Hao
2019-06-27  4:44 ` [PATCH v4 07/15] fpga: dfl: pci: enable SRIOV support Wu Hao
2019-06-27  4:44 ` [PATCH v4 08/15] fpga: dfl: afu: add AFU state related sysfs interfaces Wu Hao
2019-06-27  4:44 ` [PATCH v4 09/15] fpga: dfl: afu: add userclock " Wu Hao
2019-06-27  4:44 ` [PATCH v4 10/15] fpga: dfl: add id_table for dfl private feature driver Wu Hao
2019-06-27  4:44 ` [PATCH v4 11/15] fpga: dfl: afu: export __port_enable/disable function Wu Hao
2019-06-27  4:44 ` [PATCH v4 12/15] fpga: dfl: afu: add error reporting support Wu Hao
2019-06-27  4:44 ` [PATCH v4 13/15] fpga: dfl: afu: add STP (SignalTap) support Wu Hao
2019-06-27  4:44 ` [PATCH v4 14/15] fpga: dfl: fme: add capability sysfs interfaces Wu Hao
2019-06-27  4:44 ` [PATCH v4 15/15] fpga: dfl: fme: add global error reporting support Wu Hao

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=20190628011256.GB5671@archbook \
    --to=mdf@kernel.org \
    --cc=atull@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hao.wu@intel.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).