DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: David Marchand <david.marchand@redhat.com>, dev@dpdk.org
Cc: thomas@monjalon.net, ferruh.yigit@amd.com, gakhil@marvell.com,
	Nicolas Chautru <nicolas.chautru@intel.com>,
	Sunil Uttarwar <sunilprakashrao.uttarwar@amd.com>,
	Yuying Zhang <Yuying.Zhang@intel.com>,
	Beilei Xing <beilei.xing@intel.com>,
	Simei Su <simei.su@intel.com>, Wenjun Wu <wenjun1.wu@intel.com>,
	Qiming Yang <qiming.yang@intel.com>
Subject: Re: [PATCH] doc/guides: refer to generic binding devices section
Date: Wed, 15 Nov 2023 11:10:20 +0100	[thread overview]
Message-ID: <d952bcab-75eb-47a1-81b4-3348ea3e7cdc@redhat.com> (raw)
In-Reply-To: <20231006125500.740299-1-david.marchand@redhat.com>



On 10/6/23 14:55, David Marchand wrote:
> Rather than copy/paste everywhere how to bind a device and create VF
> devices, refer to the Linux GSG section about it.
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
>   doc/guides/bbdevs/acc100.rst        | 73 ++---------------------------
>   doc/guides/bbdevs/fpga_5gnr_fec.rst | 71 ++--------------------------
>   doc/guides/bbdevs/fpga_lte_fec.rst  | 70 ++-------------------------
>   doc/guides/bbdevs/vrb1.rst          | 66 ++------------------------
>   doc/guides/cryptodevs/ccp.rst       | 14 +-----
>   doc/guides/nics/intel_vf.rst        | 57 ++++------------------
>   6 files changed, 25 insertions(+), 326 deletions(-)
> 

Thanks David for working on this clean-up:

Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Maxime


  reply	other threads:[~2023-11-15 10:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06 12:55 David Marchand
2023-11-15 10:10 ` Maxime Coquelin [this message]
2023-11-24 12:50   ` David Marchand

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=d952bcab-75eb-47a1-81b4-3348ea3e7cdc@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=Yuying.Zhang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=gakhil@marvell.com \
    --cc=nicolas.chautru@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=simei.su@intel.com \
    --cc=sunilprakashrao.uttarwar@amd.com \
    --cc=thomas@monjalon.net \
    --cc=wenjun1.wu@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).