From: Akhil Goyal <gakhil@marvell.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Nandini Persad <nandinipersad361@gmail.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: RE: [EXTERNAL] [PATCH v2] doc: add new driver guidelines
Date: Thu, 5 Sep 2024 09:52:13 +0000 [thread overview]
Message-ID: <CO6PR18MB44843EF6875610C01D8E7A34D89D2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <aa0ee9df-68ec-4562-9f9a-d7dd2a6665c2@amd.com>
> >> +Additional Suggestions
> >> +----------------------
> >> +
> > .ini file shall be updated for each of the new feature added in the same patch as
> code.
> >
>
> This is mentioned above as:
> "Update relevant documentation and <driver>.ini file with each patch."
Ok. I missed that.
next prev parent reply other threads:[~2024-09-05 9:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 20:12 [PATCH] " Nandini Persad
2024-08-14 2:35 ` [PATCH v2] " Stephen Hemminger
2024-08-14 10:10 ` David Marchand
2024-08-14 19:08 ` Stephen Hemminger
2024-09-05 9:16 ` [EXTERNAL] " Akhil Goyal
2024-09-05 9:49 ` Ferruh Yigit
2024-09-05 9:52 ` Akhil Goyal [this message]
2024-09-06 8:05 ` fengchengwen
2024-09-06 8:27 ` Ferruh Yigit
2024-09-09 1:01 ` fengchengwen
2024-09-10 14:58 ` [PATCH v3] " Nandini Persad
2024-09-11 0:16 ` Ferruh Yigit
2024-09-11 16:04 ` Nandini Persad
2024-09-12 8:13 ` Ferruh Yigit
2024-09-12 13:18 ` Nandini Persad
2024-09-12 13:37 ` Ferruh Yigit
2024-09-12 13:40 ` Nandini Persad
2024-09-12 20:26 ` Stephen Hemminger
2024-09-13 4:19 ` WanRenyong
2024-09-13 9:07 ` Ferruh Yigit
2024-09-13 16:08 ` Stephen Hemminger
2024-09-16 16:28 ` [PATCH v4] " Stephen Hemminger
2024-09-27 0:19 ` Ferruh Yigit
2024-09-27 15:02 ` Thomas Monjalon
2024-10-04 16:39 ` [PATCH v5] " Nandini Persad
2024-10-04 18:33 ` Ferruh Yigit
2024-10-06 18:42 ` [PATCH v6] " Nandini Persad
2024-10-06 21:09 ` Ferruh Yigit
2024-10-18 17:04 ` Thomas Monjalon
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=CO6PR18MB44843EF6875610C01D8E7A34D89D2@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=nandinipersad361@gmail.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).