From: David Marchand <david.marchand@redhat.com>
To: Euan Bourke <euan.bourke@intel.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Bruce Richardson <bruce.richardson@intel.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: Re: [PATCH v2 1/2] doc: updated incorrect value for IP frag max fragments
Date: Thu, 21 Dec 2023 12:39:56 +0100 [thread overview]
Message-ID: <CAJFAV8yBw-57ymVxZKbuiJdSA+GVsXEk3W0AZhV-kfh+rSJs-A@mail.gmail.com> (raw)
In-Reply-To: <20231221113242.3351356-1-euan.bourke@intel.com>
Hello,
On Thu, Dec 21, 2023 at 12:33 PM Euan Bourke <euan.bourke@intel.com> wrote:
>
> Docs for IP Fragment said RTE_LIBRTE_IP_FRAG_MAX_FRAGS was 4 by default,
> however this was changed to 8.
>
> Documentation has been updated to account for this, including a
> snippet of the code where RTE_LIBRTE_IP_FRAG_MAX_FRAGS is defined to
> ensure the documentation stays up to date.
>
> Signed-off-by: Euan Bourke <euan.bourke@intel.com>
Fixes: tag?
--
David Marchand
next prev parent reply other threads:[~2023-12-21 11:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <https://inbox.dpdk.org/dev/20231219151754.3285058-1-euan.bourke@intel.com/>
2023-12-21 11:32 ` Euan Bourke
2023-12-21 11:32 ` [PATCH v2 2/2] ip_frag: updated name for IP frag define Euan Bourke
2023-12-21 11:39 ` David Marchand [this message]
2023-12-21 11:41 ` [PATCH v2 1/2] doc: updated incorrect value for IP frag max fragments Thomas Monjalon
2023-12-21 13:46 ` Bourke, Euan
2023-12-21 17:41 ` [PATCH v3 " Euan Bourke
2023-12-21 17:41 ` [PATCH v3 2/2] ip_frag: updated name for IP frag max frag define Euan Bourke
2023-12-22 9:08 ` Bruce Richardson
2024-01-08 11:36 ` [PATCH v4 1/2] doc: updated incorrect value for IP frag max fragments Euan Bourke
2024-01-08 11:36 ` [PATCH v4 2/2] ip_frag: updated name for IP frag define Euan Bourke
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=CAJFAV8yBw-57ymVxZKbuiJdSA+GVsXEk3W0AZhV-kfh+rSJs-A@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=euan.bourke@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
--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).