From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Erwan Velu <erwanaliasr1@gmail.com>, Paolo Abeni <pabeni@redhat.com>
Cc: Erwan Velu <e.velu@criteo.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] i40e: Prevent setting MTU if greater than MFS
Date: Tue, 12 Mar 2024 15:07:44 -0700 [thread overview]
Message-ID: <c35ee088-9502-41e4-b47d-c42ad9c5fb24@intel.com> (raw)
In-Reply-To: <CAL2JzuxA1h=L=0cr+Q6CZ9UDbHB6ptbzCQ7gZddZLi2JumdLQQ@mail.gmail.com>
On 3/12/2024 3:29 AM, Erwan Velu wrote:
>> On Tue, 2024-03-12 at 10:42 +0100, Erwan Velu wrote:
>
>> This looks like a legit fix that should target the 'net' tree, @Tony:
>> do you agree?
>> If so, Erwan, please include a suitable fixes tag in the next revision.
>> Please include into the subj prefix a suitable target tree. I think
>> this should go first via the intel tree for testing, so 'iwl-net'
>> should fit.
> Oh I didn't knew that part, thx. I'll wait @Tony to see what target I
> should use.
I agree with both parts, so 'iwl-net' would be best.
Thanks,
Tony
>
>> In any case please respect the 24h grace period when posting on netdev:
> Yeah sorry for the v3 ... I shouldn't have done that way, that fast.
prev parent reply other threads:[~2024-03-12 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 9:42 [PATCH v3] i40e: Prevent setting MTU if greater than MFS Erwan Velu
2024-03-12 9:48 ` [Intel-wired-lan] " Paul Menzel
2024-03-12 10:18 ` Erwan Velu
2024-03-12 10:01 ` Paolo Abeni
2024-03-12 10:29 ` Erwan Velu
2024-03-12 22:07 ` Tony Nguyen [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=c35ee088-9502-41e4-b47d-c42ad9c5fb24@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=e.velu@criteo.com \
--cc=edumazet@google.com \
--cc=erwanaliasr1@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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