From: Kevin Traynor <ktraynor@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: stable@dpdk.org, bluca@debian.org, john.mcnamara@intel.com,
qi.z.zhang@intel.com, yux.jiang@intel.com, beilei.xing@intel.com,
Yuying.Zhang@intel.com, wenxuanx.wu@intel.com,
jie1x.wang@intel.com, dapengx.yu@intel.com
Subject: Re: [PATCH 21.11 1/3] Revert "net/i40e: fix jumbo frame Rx with X722"
Date: Mon, 19 Dec 2022 10:20:13 +0000 [thread overview]
Message-ID: <d70553c7-5f30-5944-d291-371b6ccc0336@redhat.com> (raw)
In-Reply-To: <CAJFAV8w1ZrNQktWDdOHJrQL0=7PS-Q591MF6fQ-mqO9C0Nz3_w@mail.gmail.com>
On 14/12/2022 10:19, David Marchand wrote:
> On Tue, Dec 13, 2022 at 7:48 PM Kevin Traynor <ktraynor@redhat.com> wrote:
>>
>> This reverts commit 46abe3043e56f4905972ad87f1bfb15f4c1bc4a2.
>>
>> This chain of commits has been found to cause issues with setting
>> max frame size when the link is not negotiated in 1s or the link
>> is down. The frame size is not set and no error is returned to
>> the user.
>>
>> Revert the chain until a fix is found.
>>
>> Link to original upstream commit and discussion:
>> 719469f13b11 ("net/i40e: fix jumbo frame Rx with X722")
>> https://mails.dpdk.org/archives/dev/2022-December/257566.html
>>
>> Reported-by: David Marchand <david.marchand@redhat.com>
>> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
>
> For the series,
> Acked-by: David Marchand <david.marchand@redhat.com>
>
>
Thanks David. No review from authors/i40e maintainers :/
Applied and pushed to 21.11 branch.
prev parent reply other threads:[~2022-12-19 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 18:47 Kevin Traynor
2022-12-13 18:47 ` [PATCH 21.11 2/3] Revert "net/i40e: fix max frame size config at port level" Kevin Traynor
2022-12-13 18:47 ` [PATCH 21.11 3/3] Revert "net/i40e: enable maximum frame size " Kevin Traynor
2022-12-14 10:19 ` [PATCH 21.11 1/3] Revert "net/i40e: fix jumbo frame Rx with X722" David Marchand
2022-12-19 10:20 ` Kevin Traynor [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=d70553c7-5f30-5944-d291-371b6ccc0336@redhat.com \
--to=ktraynor@redhat.com \
--cc=Yuying.Zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=bluca@debian.org \
--cc=dapengx.yu@intel.com \
--cc=david.marchand@redhat.com \
--cc=jie1x.wang@intel.com \
--cc=john.mcnamara@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=wenxuanx.wu@intel.com \
--cc=yux.jiang@intel.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).