Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Petr Oros <poros@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "Laba, SlawomirX" <slawomirx.laba@intel.com>,
	"Maziarz, Kamil" <kamil.maziarz@intel.com>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"Zulinski, NorbertX" <norbertx.zulinski@intel.com>,
	"dawidx.wesierski@intel.com" <dawidx.wesierski@intel.com>,
	"edumazet@google.com" <edumazet@google.com>,
	"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
	"horms@kernel.org" <horms@kernel.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH net v2 0/2] Fix VF to VM attach detach
Date: Thu, 10 Aug 2023 14:52:33 +0200	[thread overview]
Message-ID: <38f4dcfd-ccee-3481-a862-58b269bc0acc@intel.com> (raw)
In-Reply-To: <20230809151529.842798-1-poros@redhat.com>

On 8/9/23 17:15, Petr Oros wrote:
> 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(-)
> 

You have forgot to propagate reviewed-by tags from v1 (Simon's, Jake's, 
mine)

Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>

(I'm not sure if I should copy-paste not mine RBs here?)
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  parent reply	other threads:[~2023-08-10 12:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 15:15 [Intel-wired-lan] [PATCH net v2 0/2] Fix VF to VM attach detach Petr Oros
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 ` Przemek Kitszel [this message]
2023-08-10 15:51   ` [Intel-wired-lan] [PATCH net v2 0/2] Fix VF to VM attach detach 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=38f4dcfd-ccee-3481-a862-58b269bc0acc@intel.com \
    --to=przemyslaw.kitszel@intel.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=poros@redhat.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