From: Jacob Keller <jacob.e.keller@intel.com>
To: Li Li <boolli@google.com>
Cc: Simon Horman <horms@kernel.org>, <anthony.l.nguyen@intel.com>,
<przemyslaw.kitszel@intel.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <edumazet@google.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <decot@google.com>,
<anjali.singhai@intel.com>, <sridhar.samudrala@intel.com>,
<brianvv@google.com>, <emil.s.tantilov@intel.com>,
<stable@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-net v2] idpf: do not perform flow ops when netdev is detached
Date: Thu, 30 Apr 2026 15:46:21 -0700 [thread overview]
Message-ID: <4c2b3c63-4668-498e-9c4a-a135da5cd5b3@intel.com> (raw)
In-Reply-To: <CAODvEq4R_7SXfo5QJ0z=fM5npz1ZFFcCQTTKkdoLKtXyoDnjRA@mail.gmail.com>
On 4/30/2026 1:58 PM, Li Li wrote:
> Yes, OpenOnload calls idpf_set_rxnfc directly without checking if the
> netdev is detached first. I've discussed this with the team
> internally, and we decided to fix OpenOnload directly, rather than
> adding the check in idpf.
>
> Please feel free to drop this patch, thank you!
I've dropped the patch from Intel Wired LAN patchworks. Thanks!
prev parent reply other threads:[~2026-04-30 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 5:16 [Intel-wired-lan] [PATCH iwl-net v2] idpf: do not perform flow ops when netdev is detached Li Li via Intel-wired-lan
2026-04-23 16:33 ` Simon Horman
2026-04-23 18:40 ` Jacob Keller
2026-04-30 20:58 ` Li Li via Intel-wired-lan
2026-04-30 22:46 ` Jacob Keller [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=4c2b3c63-4668-498e-9c4a-a135da5cd5b3@intel.com \
--to=jacob.e.keller@intel.com \
--cc=anjali.singhai@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=boolli@google.com \
--cc=brianvv@google.com \
--cc=davem@davemloft.net \
--cc=decot@google.com \
--cc=edumazet@google.com \
--cc=emil.s.tantilov@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=sridhar.samudrala@intel.com \
--cc=stable@vger.kernel.org \
/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