From: "Thomas Monjalon" <thomas@monjalon.net>
To: "Ferruh Yigit" <ferruh.yigit@intel.com>,
"David Marchand" <david.marchand@redhat.com>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"Jerin Jacob Kollanukkaran" <jerinj@marvell.com>,
"Maxime Coquelin" <maxime.coquelin@redhat.com>,
"Qi Zhang" <qi.z.zhang@intel.com>,
"Raslan Darawsheh" <rasland@nvidia.com>,
"Ajit Khaparde" <ajit.khaparde@broadcom.com>
Cc: dev@dpdk.org, "Heinrich Kuhn" <heinrich.kuhn@netronome.com>,
"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] doc: fix nfp multiport syntax
Date: Mon, 26 Apr 2021 15:51:09 +0200 [thread overview]
Message-ID: <e1606fe4-7150-4b7a-91c3-f4f33f7e0adb@www.fastmail.com> (raw)
In-Reply-To: <b3c0e942-83ca-8e9a-0b59-2bca7350f68b@intel.com>
Lun 26 avr 2021, à 11:48, Ferruh Yigit a écrit :
> Hi Thomas, David, Akhil, Jerin, Maxime, Qi, Raslan, Ajit,
>
> For the doc patches, the subsystem prefix 'doc:' is too wide, what do you think
> to extend it to include the component, like for this patch:
> "doc/nics/nfp: fix multiport syntax"
Usually I format like this:
doc: fix multiport syntax in nfp guide
I am not sure about being precise in the doc prefix for 2 reasons:
- the doc hierarchy can be quite complex
- it may give too much importance visually to the doc changes
But if everybody prefer a precise prefix, I am OK to change the habit.
prev parent reply other threads:[~2021-04-26 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 11:46 [dpdk-dev] " Heinrich Kuhn
2021-03-01 13:45 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2021-04-23 16:18 ` Ferruh Yigit
2021-04-26 9:46 ` Ferruh Yigit
2021-04-26 9:48 ` Ferruh Yigit
2021-04-26 13:51 ` Thomas Monjalon [this message]
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=e1606fe4-7150-4b7a-91c3-f4f33f7e0adb@www.fastmail.com \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gakhil@marvell.com \
--cc=heinrich.kuhn@netronome.com \
--cc=jerinj@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=qi.z.zhang@intel.com \
--cc=rasland@nvidia.com \
--cc=techboard@dpdk.org \
/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).