From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Ivan Vecera <ivecera@redhat.com>, <netdev@vger.kernel.org>
Cc: <aleksandr.loktionov@intel.com>, <mschmidt@redhat.com>,
<horms@kernel.org>, Jesse Brandeburg <jesse.brandeburg@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
"moderated list:INTEL ETHERNET DRIVERS"
<intel-wired-lan@lists.osuosl.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] i40e: Fix VF MAC filter removal
Date: Wed, 27 Mar 2024 11:10:01 -0700 [thread overview]
Message-ID: <e6581461-5589-ffaf-498e-5737dd48a7f8@intel.com> (raw)
In-Reply-To: <8e585156-4f6f-4837-9375-f29842fa7f85@redhat.com>
On 3/27/2024 12:29 AM, Ivan Vecera wrote:
...
> Hi Tony,
> the fix is not part of your recent pull series for i40e... I have
> submitted it to 'net' instead of 'iwl-net' as it fixes recent commit
> that causes MAC filter resource leaks that should be fixed as soon as
> possible. But its status in patchwork is 'Awaiting upstream' so it has
> to be resubmitted by yourself... Or should this be picked directly by
> netdev maintainers?
Hi Ivan,
The normal process is that it goes through the IWL trees. It's currently
applied to the tree awaiting our validation's tested-by. I will send it
on after that occurs.
Thanks,
Tony
> Thanks,
> Ivan
>
prev parent reply other threads:[~2024-03-27 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 13:56 [PATCH net] i40e: Fix VF MAC filter removal Ivan Vecera
2024-03-14 11:57 ` Michal Schmidt
2024-03-14 15:54 ` Brett Creeley
2024-03-28 16:10 ` [Intel-wired-lan] " Romanowski, Rafal
2024-03-27 7:29 ` Ivan Vecera
2024-03-27 18:10 ` 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=e6581461-5589-ffaf-498e-5737dd48a7f8@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--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