From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbo.xia@intel.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v2] kni: remove deprecated kernel network interface
Date: Tue, 1 Aug 2023 09:33:29 +0200 [thread overview]
Message-ID: <CAJFAV8wx-6Wpq8pc9vnupg9fY9oqtDsnyt8TnwnJUeasPuTjpQ@mail.gmail.com> (raw)
In-Reply-To: <20230730021206.6381-1-stephen@networkplumber.org>
Hello Stephen,
While rebasing, please also fix those nits:
On Sun, Jul 30, 2023 at 4:12 AM Stephen Hemminger
<stephen@networkplumber.org> wrote:
> diff --git a/doc/guides/contributing/documentation.rst b/doc/guides/contributing/documentation.rst
> index 7fcbb7fc43b2..f16c94e9768b 100644
> --- a/doc/guides/contributing/documentation.rst
> +++ b/doc/guides/contributing/documentation.rst
> @@ -95,7 +95,7 @@ added to by the developer.
> * **The Programmers Guide**
>
> The Programmers Guide explains how the API components of DPDK such as the EAL, Memzone, Rings and the Hash Library work.
> - It also explains how some higher level functionality such as Packet Distributor, Packet Framework and KNI work.
> + It also explains how some higher level functionality such as Packet Distributor and Packet Framework.
s/how some higher level functionality/how some higher level functionality work/
> It also shows the build system and explains how to add applications.
>
> The Programmers Guide should be expanded when new functionality is added to DPDK.
[snip]
> diff --git a/doc/guides/rel_notes/release_23_11.rst b/doc/guides/rel_notes/release_23_11.rst
> new file mode 100644
> index 000000000000..e2158934751f
> --- /dev/null
> +++ b/doc/guides/rel_notes/release_23_11.rst
> @@ -0,0 +1,16 @@
> +.. SPDX-License-Identifier: BSD-3-Clause
> + Copyright 2022 The DPDK contributors
> +
> +.. include:: <isonum.txt>
> +
> +DPDK Release 23.11
> +==================
> +
> +New Features
> +------------
> +
> +
> +Removed Items
> +-------------
> +
> +* kni: Remove deprecated Kernel Network Interface driver, libraries and examples
s/Remove/Removed/
s/$/./
Thanks.
--
David Marchand
prev parent reply other threads:[~2023-08-01 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 22:54 [PATCH] " Stephen Hemminger
2023-07-30 2:12 ` [PATCH v2] " Stephen Hemminger
2023-07-30 17:12 ` Stephen Hemminger
2023-07-31 8:40 ` Thomas Monjalon
2023-07-31 15:13 ` Stephen Hemminger
2023-07-31 15:21 ` David Marchand
2023-07-31 15:35 ` Thomas Monjalon
2023-07-31 21:12 ` Stephen Hemminger
2023-07-31 21:27 ` Thomas Monjalon
2023-08-01 7:33 ` David Marchand [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=CAJFAV8wx-6Wpq8pc9vnupg9fY9oqtDsnyt8TnwnJUeasPuTjpQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chenbo.xia@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=kirankumark@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).