From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Cc: ferruh.yigit@intel.com, david.marchand@redhat.com,
bruce.richardson@intel.com, olivier.matz@6wind.com,
akhil.goyal@nxp.com, stable@dpdk.org,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-stable] [PATCH 03/15] mbuf: fix typo in dynamic field convention note
Date: Mon, 26 Oct 2020 17:26:23 +0300 [thread overview]
Message-ID: <5122ee5c-6deb-8e7f-e96e-bbd992963a13@oktetlabs.ru> (raw)
In-Reply-To: <20201026052105.1561859-4-thomas@monjalon.net>
On 10/26/20 8:20 AM, Thomas Monjalon wrote:
> Replace "in a in PMD" with "in a PMD".
>
> Fixes: 4958ca3a443a ("mbuf: support dynamic fields and flags")
> 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:[~2020-10-26 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201026052105.1561859-1-thomas@monjalon.net>
2020-10-26 5:20 ` Thomas Monjalon
2020-10-26 14:26 ` Andrew Rybchenko [this message]
[not found] ` <20201026222013.2147904-1-thomas@monjalon.net>
2020-10-26 22:20 ` [dpdk-stable] [PATCH v2 " Thomas Monjalon
[not found] ` <20201027210115.2529025-1-thomas@monjalon.net>
2020-10-27 21:01 ` [dpdk-stable] [PATCH v3 " Thomas Monjalon
[not found] ` <20201028102640.3191964-1-thomas@monjalon.net>
2020-10-28 10:26 ` [dpdk-stable] [PATCH v4 " Thomas Monjalon
[not found] ` <20201030172940.1073558-1-thomas@monjalon.net>
2020-10-30 17:29 ` [dpdk-stable] [PATCH v5 07/15] net/mlx5: fix dynamic mbuf offset lookup check Thomas Monjalon
[not found] ` <20201030174441.1076264-1-thomas@monjalon.net>
2020-10-30 17:44 ` [dpdk-stable] [PATCH v6 03/15] mbuf: fix typo in dynamic field convention note 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=5122ee5c-6deb-8e7f-e96e-bbd992963a13@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=akhil.goyal@nxp.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=olivier.matz@6wind.com \
--cc=stable@dpdk.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).