From: Thomas Monjalon <thomas@monjalon.net>
To: Gerry Gribbon <ggribbon@nvidia.com>
Cc: dev@dpdk.org, jamhunter@nvidia.com, orika@nvidia.com,
stephen@networkplumber.org
Subject: Re: [PATCH v2] regexdev: add maximum number of mbuf segments field
Date: Sun, 09 Oct 2022 14:56:34 +0200 [thread overview]
Message-ID: <1874720.6tgchFWduM@thomas> (raw)
In-Reply-To: <20221007080422.280482-1-ggribbon@nvidia.com>
07/10/2022 10:04, Gerry Gribbon:
> Allows application to query maximum number of mbuf segments that can
> be chained together.
>
> Signed-off-by: Gerry Gribbon <ggribbon@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
Applied, thanks.
prev parent reply other threads:[~2022-10-09 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 8:16 [PATCH] " Gerry Gribbon
2022-09-01 8:16 ` Gerry Gribbon
2022-10-07 8:04 ` [PATCH v2] " Gerry Gribbon
2022-10-09 12:56 ` 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=1874720.6tgchFWduM@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ggribbon@nvidia.com \
--cc=jamhunter@nvidia.com \
--cc=orika@nvidia.com \
--cc=stephen@networkplumber.org \
/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).