From: Petr Oros <poros@redhat.com>
To: netdev@vger.kernel.org
Cc: slawomirx.laba@intel.com, przemyslawx.patynowski@intel.com,
kamil.maziarz@intel.com, jesse.brandeburg@intel.com,
norbertx.zulinski@intel.com, dawidx.wesierski@intel.com,
edumazet@google.com, przemyslaw.kitszel@intel.com,
anthony.l.nguyen@intel.com, horms@kernel.org,
intel-wired-lan@lists.osuosl.org, kuba@kernel.org,
pabeni@redhat.com, davem@davemloft.net,
linux-kernel@vger.kernel.org
Subject: [Intel-wired-lan] [PATCH net v2 0/2] Fix VF to VM attach detach
Date: Wed, 9 Aug 2023 17:15:27 +0200 [thread overview]
Message-ID: <20230809151529.842798-1-poros@redhat.com> (raw)
v2: fixed typos in the description of the second patch
v1: https://lore.kernel.org/netdev/20230807094831.696626-1-poros@redhat.com/
Petr Oros (2):
Revert "ice: Fix ice VF reset during iavf initialization"
ice: Fix NULL pointer deref during VF reset
drivers/net/ethernet/intel/ice/ice_sriov.c | 8 ++---
drivers/net/ethernet/intel/ice/ice_vf_lib.c | 34 +++++--------------
drivers/net/ethernet/intel/ice/ice_vf_lib.h | 1 -
drivers/net/ethernet/intel/ice/ice_virtchnl.c | 1 -
4 files changed, 12 insertions(+), 32 deletions(-)
--
2.41.0
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2023-08-09 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 15:15 Petr Oros [this message]
2023-08-09 15:15 ` [Intel-wired-lan] [PATCH net v2 1/2] Revert "ice: Fix ice VF reset during iavf initialization" Petr Oros
2023-08-09 15:15 ` [Intel-wired-lan] [PATCH net v2 2/2] ice: Fix NULL pointer deref during VF reset Petr Oros
2023-08-10 12:52 ` [Intel-wired-lan] [PATCH net v2 0/2] Fix VF to VM attach detach Przemek Kitszel
2023-08-10 15:51 ` Jakub Kicinski
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=20230809151529.842798-1-poros@redhat.com \
--to=poros@redhat.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dawidx.wesierski@intel.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kamil.maziarz@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=norbertx.zulinski@intel.com \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=przemyslawx.patynowski@intel.com \
--cc=slawomirx.laba@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