From: Thomas Monjalon <thomas@monjalon.net>
To: Bing Zhao <bingz@nvidia.com>
Cc: matan@nvidia.com, viacheslavo@nvidia.com, valex@nvidia.com,
rasland@nvidia.com, dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH v2] doc: fix the template API requirements
Date: Thu, 20 Jul 2023 04:39:02 +0200 [thread overview]
Message-ID: <2689038.kXSN5OTJKJ@thomas> (raw)
In-Reply-To: <20230719153537.189113-1-bingz@nvidia.com>
19/07/2023 17:35, Bing Zhao:
> The minimal SW and HW versions are added.
>
> Fixes: 22681deead3e ("net/mlx5/hws: enable hardware steering")
> Cc: valex@nvidia.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Bing Zhao <bingz@nvidia.com>
Applied as "doc: add flow template API requirements for mlx5"
prev parent reply other threads:[~2023-07-20 2:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 9:34 [PATCH] net/mlx5: " Bing Zhao
2023-07-19 15:35 ` [PATCH v2] doc: " Bing Zhao
2023-07-20 2:39 ` Thomas Monjalon [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=2689038.kXSN5OTJKJ@thomas \
--to=thomas@monjalon.net \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=valex@nvidia.com \
--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).