From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
Thomas Monjalon <thomas@monjalon.net>, Ori Kam <orika@nvidia.com>,
Wenjun Wu <wenjun1.wu@intel.com>, Jie Wang <jie1x.wang@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: David Marchand <david.marchand@redhat.com>,
dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH v5 7/8] doc: fix description of L2TPV2 flow item
Date: Thu, 2 Feb 2023 12:56:47 +0300 [thread overview]
Message-ID: <66e2c048-fbd1-7caf-4648-08cbb54ca8f0@oktetlabs.ru> (raw)
In-Reply-To: <20230126161904.864517-8-ferruh.yigit@amd.com>
On 1/26/23 19:19, Ferruh Yigit wrote:
> From: Thomas Monjalon <thomas@monjalon.net>
>
> The flow item structure includes the protocol definition
> from the directory lib/net/, so it is reflected in the guide.
>
> Section title underlining is also fixed around.
>
> Fixes: 3a929df1f286 ("ethdev: support L2TPv2 and PPP procotol")
> Cc: stable@dpdk.org
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
next prev parent reply other threads:[~2023-02-02 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221025214410.715864-1-thomas@monjalon.net>
[not found] ` <20230120171902.4188088-1-ferruh.yigit@amd.com>
2023-01-20 17:19 ` [PATCH v2 " Ferruh Yigit
[not found] ` <20230124090300.247915-1-ferruh.yigit@amd.com>
2023-01-24 9:02 ` [PATCH v3 " Ferruh Yigit
[not found] ` <20230126131759.3887632-1-ferruh.yigit@amd.com>
2023-01-26 13:17 ` [PATCH v4 " Ferruh Yigit
[not found] ` <20230126161904.864517-1-ferruh.yigit@amd.com>
2023-01-26 16:19 ` [PATCH v5 " Ferruh Yigit
2023-02-02 9:56 ` Andrew Rybchenko [this message]
[not found] ` <20230202124500.2578857-1-ferruh.yigit@amd.com>
2023-02-02 12:44 ` [PATCH v6 " Ferruh Yigit
[not found] ` <20230203164854.602595-1-ferruh.yigit@amd.com>
2023-02-03 16:48 ` [PATCH v7 6/7] " Ferruh Yigit
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=66e2c048-fbd1-7caf-4648-08cbb54ca8f0@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=ferruh.yigit@intel.com \
--cc=jie1x.wang@intel.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--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).