From: Stephen Hemminger <stephen@networkplumber.org>
To: Bing Zhao <bingz@nvidia.com>
Cc: <viacheslavo@nvidia.com>, <matan@nvidia.com>, <dev@dpdk.org>,
<rasland@nvidia.com>, <stable@dpdk.org>
Subject: Re: [PATCH] doc: fix the typo of hexadecimal writing
Date: Fri, 30 Jun 2023 14:33:25 -0700 [thread overview]
Message-ID: <20230630143325.39cbe254@hermes.local> (raw)
In-Reply-To: <20211126085957.15691-1-bingz@nvidia.com>
On Fri, 26 Nov 2021 10:59:57 +0200
Bing Zhao <bingz@nvidia.com> wrote:
> A leading '0' was missed of the hexadecimal value.
>
> Fixes: 3ceeed9f7855 ("doc: update flow mark action in mlx5 guide")
> Cc: viacheslavo@nvidia.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Bing Zhao <bingz@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
This was already fixed
prev parent reply other threads:[~2023-06-30 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 8:59 Bing Zhao
2023-06-30 21:33 ` Stephen Hemminger [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=20230630143325.39cbe254@hermes.local \
--to=stephen@networkplumber.org \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.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).