DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: "Xu, Rosen" <rosen.xu@intel.com>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 Shepard Siegel <shepard.siegel@atomicrules.com>,
	Ed Czeck <ed.czeck@atomicrules.com>,
	 John Miller <john.miller@atomicrules.com>,
	Somalapuram Amaranath <asomalap@amd.com>,
	 Rasesh Mody <rmody@marvell.com>,
	Shahed Shaikh <shshaikh@marvell.com>,
	 Somnath Kotur <somnath.kotur@broadcom.com>,
	 Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	 Sachin Saxena <sachin.saxena@oss.nxp.com>,
	Marcin Wojtas <mw@semihalf.com>,
	 Michal Krawczyk <mk@semihalf.com>,
	Guy Tzalik <gtzalik@amazon.com>,
	 Evgeny Schemeilin <evgenys@amazon.com>,
	Igor Chauskin <igorch@amazon.com>,
	 Gagandeep Singh <g.singh@nxp.com>, Gaetan Rivet <grive@u256.net>,
	Ziyang Xuan <xuanziyang2@huawei.com>,
	 Xiaoyun Wang <cloud.wangxiaoyun@huawei.com>,
	Guoyang Zhou <zhouguoyang@huawei.com>,
	 "Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
	"Min Hu (Connor)" <humin29@huawei.com>,
	 Yisen Zhuang <yisen.zhuang@huawei.com>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"Guo, Jia" <jia.guo@intel.com>,
	"Yang, Qiming" <qiming.yang@intel.com>,
	 "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Wang, Haiyue" <haiyue.wang@intel.com>,
	 Shijith Thotton <sthotton@marvell.com>,
	 Srisivasubramanian Srinivasan <srinivasan@marvell.com>,
	Matan Azrad <matan@nvidia.com>,
	Shahaf Shuler <shahafs@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	 Zyta Szpak <zr@semihalf.com>, Liron Himi <lironh@marvell.com>,
	Harman Kalra <hkalra@marvell.com>,
	 Jerin Jacob <jerinj@marvell.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	 Kiran Kumar K <kirankumark@marvell.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	 Maciej Czekaj <mczekaj@marvell.com>,
	Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-dev] [PATCH 5/8] doc: fix driver names in NIC devices guide
Date: Mon, 2 Nov 2020 18:47:22 -0800	[thread overview]
Message-ID: <CACZ4nht2QnymYwpcagF6Q+Zz=s9qYBWSBHCe2PDj4D6sxPG5-Q@mail.gmail.com> (raw)
In-Reply-To: <BYAPR11MB2901ECFF51EF28D0A4F8EFFB89110@BYAPR11MB2901.namprd11.prod.outlook.com>

On Mon, Nov 2, 2020 at 6:31 PM Xu, Rosen <rosen.xu@intel.com> wrote:
>
>
>
> > Subject: [PATCH 5/8] doc: fix driver names in NIC devices guide
> >
> > Since the built driver filenames have changed in DPDK 20.11, we need to
> > update the driver doc to match.
> >
> > Most drivers start their section with the driver filename highlighted in bold,
> > while a number were missing the highlight. When updating the names, add
> > the markers for bold text to any missing it, so as to have things more
> > consistent.
> >
> > Fixes: a20b2c01a7a1 ("build: standardize component names and defines")
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>

Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>

>
>
>

  reply	other threads:[~2020-11-03  2:47 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 17:44 [dpdk-dev] [PATCH 0/8] fix driver filenames in the docs Bruce Richardson
2020-11-02 17:45 ` [dpdk-dev] [PATCH 1/8] regex/octeontx2: fix unnecessary name override Bruce Richardson
2020-11-02 19:48   ` David Marchand
2020-11-03  0:30     ` Thomas Monjalon
2020-11-03  8:19       ` David Marchand
2020-11-03  9:06         ` Thomas Monjalon
2020-11-03  9:19           ` David Marchand
2020-11-03  9:45             ` David Marchand
2020-11-03 10:27               ` Bruce Richardson
2020-11-02 17:45 ` [dpdk-dev] [PATCH 2/8] doc: fix driver names in compression devices guide Bruce Richardson
2020-11-02 19:54   ` David Marchand
2020-11-02 17:45 ` [dpdk-dev] [PATCH 3/8] doc: fix driver names in crypto " Bruce Richardson
2020-11-02 20:00   ` David Marchand
2020-11-02 20:02     ` David Marchand
2020-11-03 10:28       ` Bruce Richardson
2020-11-02 17:45 ` [dpdk-dev] [PATCH 4/8] doc: fix driver names in event " Bruce Richardson
2020-11-02 20:03   ` David Marchand
2020-11-02 17:45 ` [dpdk-dev] [PATCH 5/8] doc: fix driver names in NIC " Bruce Richardson
2020-11-02 20:17   ` David Marchand
2020-11-02 20:45     ` David Marchand
2020-11-03  2:31   ` Xu, Rosen
2020-11-03  2:47     ` Ajit Khaparde [this message]
2020-11-02 17:45 ` [dpdk-dev] [PATCH 6/8] doc: fix driver names in regex " Bruce Richardson
2020-11-02 20:07   ` David Marchand
2020-11-02 17:45 ` [dpdk-dev] [PATCH 7/8] doc: fix driver names in vDPA " Bruce Richardson
2020-11-02 20:09   ` David Marchand
2020-11-02 17:45 ` [dpdk-dev] [PATCH 8/8] doc: fix driver names in programmers guide Bruce Richardson
2020-11-02 20:12   ` David Marchand
2020-11-02 20:19 ` [dpdk-dev] [PATCH 0/8] fix driver filenames in the docs David Marchand
2020-11-03 12:36 ` [dpdk-dev] [PATCH v2 0/7] " Bruce Richardson
2020-11-03 12:36   ` [dpdk-dev] [PATCH v2 1/7] doc: fix driver names in compression devices guide Bruce Richardson
2020-11-03 12:36   ` [dpdk-dev] [PATCH v2 2/7] doc: fix driver names in crypto " Bruce Richardson
2020-11-03 13:05     ` David Marchand
2020-11-03 12:36   ` [dpdk-dev] [PATCH v2 3/7] doc: fix driver names in event " Bruce Richardson
2020-11-03 12:36   ` [dpdk-dev] [PATCH v2 4/7] doc: fix driver names in NIC " Bruce Richardson
2020-11-03 12:36   ` [dpdk-dev] [PATCH v2 5/7] doc: fix driver names in regex " Bruce Richardson
2020-11-03 12:36   ` [dpdk-dev] [PATCH v2 6/7] doc: fix driver names in vDPA " Bruce Richardson
2020-11-03 12:36   ` [dpdk-dev] [PATCH v2 7/7] doc: fix driver names in programmers guide Bruce Richardson
2020-11-03 14:50   ` [dpdk-dev] [PATCH v2 0/7] fix driver filenames in the docs 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='CACZ4nht2QnymYwpcagF6Q+Zz=s9qYBWSBHCe2PDj4D6sxPG5-Q@mail.gmail.com' \
    --to=ajit.khaparde@broadcom.com \
    --cc=akhil.goyal@nxp.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=asomalap@amd.com \
    --cc=beilei.xing@intel.com \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=cloud.wangxiaoyun@huawei.com \
    --cc=dev@dpdk.org \
    --cc=ed.czeck@atomicrules.com \
    --cc=evgenys@amazon.com \
    --cc=ferruh.yigit@intel.com \
    --cc=g.singh@nxp.com \
    --cc=grive@u256.net \
    --cc=gtzalik@amazon.com \
    --cc=haiyue.wang@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=hkalra@marvell.com \
    --cc=humin29@huawei.com \
    --cc=igorch@amazon.com \
    --cc=jerinj@marvell.com \
    --cc=jia.guo@intel.com \
    --cc=john.miller@atomicrules.com \
    --cc=kirankumark@marvell.com \
    --cc=lironh@marvell.com \
    --cc=matan@nvidia.com \
    --cc=mczekaj@marvell.com \
    --cc=mk@semihalf.com \
    --cc=mw@semihalf.com \
    --cc=ndabilpuram@marvell.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=rahul.lakkireddy@chelsio.com \
    --cc=rmody@marvell.com \
    --cc=rosen.xu@intel.com \
    --cc=sachin.saxena@oss.nxp.com \
    --cc=shahafs@nvidia.com \
    --cc=shepard.siegel@atomicrules.com \
    --cc=shshaikh@marvell.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=srinivasan@marvell.com \
    --cc=sthotton@marvell.com \
    --cc=viacheslavo@nvidia.com \
    --cc=xavier.huwei@huawei.com \
    --cc=xuanziyang2@huawei.com \
    --cc=yisen.zhuang@huawei.com \
    --cc=zhouguoyang@huawei.com \
    --cc=zr@semihalf.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).