From: Thomas Monjalon <thomas@monjalon.net>
To: Gregory Etelson <getelson@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
Matan Azrad <matan@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [PATCH 2/2] doc: update MLX5 LRO limitation
Date: Tue, 22 Nov 2022 09:25:52 +0100 [thread overview]
Message-ID: <4226852.ejJDZkT8p0@thomas> (raw)
In-Reply-To: <IA1PR12MB6332CDF178D6466C8E2FDF84A50D9@IA1PR12MB6332.namprd12.prod.outlook.com>
22/11/2022 06:17, Gregory Etelson:
> Hello Thomas,
>
> > > .. note::
> > >
> > > MAC addresses not already present in the bridge table of the
> > associated
> >
> > If you would like to read the doc, I guess you'd prefer to find this info
> > in the section dedicated to LRO, not in a random place.
> >
> I moved the patch location in v2
I've fixed v1 and merged yesterday. No need for v2.
next prev parent reply other threads:[~2022-11-22 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221117143901.27957-1-getelson@nvidia.com>
2022-11-17 14:39 ` Gregory Etelson
2022-11-21 15:23 ` Thomas Monjalon
2022-11-22 5:17 ` Gregory Etelson
2022-11-22 8:25 ` Thomas Monjalon [this message]
[not found] ` <20221122051308.194-1-getelson@nvidia.com>
2022-11-22 5:13 ` [PATCH v2 " Gregory Etelson
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=4226852.ejJDZkT8p0@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--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).