All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Vecera <ivecera@redhat.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net] ice: Protect vf_state check by cfg_lock in ice_vc_process_vf_msg()
Date: Tue, 19 Apr 2022 16:23:02 +0200	[thread overview]
Message-ID: <20220419162302.60378ede@ceranb> (raw)
In-Reply-To: <607248b2-bfb2-08a2-3d17-67c5c28840fc@intel.com>

On Mon, 18 Apr 2022 11:10:30 -0700
Tony Nguyen <anthony.l.nguyen@intel.com> wrote:

> > If you want to leave the code as is and remove this from the patch
> > let me know and I will send v2.  
> 
> The change itself looks ok to me, but for net patches, we should fix the 
> issue without introducing other changes. A v2 without this change would 
> be great; feel free to submit this change to -next after I've applied 
> the v2 for this patch.
> 
> Thanks,
> 
> Tony
Agree, sending v2.

Thanks,
Ivan


WARNING: multiple messages have this Message-ID (diff)
From: Ivan Vecera <ivecera@redhat.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
	Fei Liu <feliu@redhat.com>, <netdev@vger.kernel.org>,
	<mschmidt@redhat.com>, "Brett Creeley" <brett@pensando.io>,
	open list <linux-kernel@vger.kernel.org>,
	"moderated list:INTEL ETHERNET DRIVERS" 
	<intel-wired-lan@lists.osuosl.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH net] ice: Protect vf_state check by cfg_lock in ice_vc_process_vf_msg()
Date: Tue, 19 Apr 2022 16:23:02 +0200	[thread overview]
Message-ID: <20220419162302.60378ede@ceranb> (raw)
In-Reply-To: <607248b2-bfb2-08a2-3d17-67c5c28840fc@intel.com>

On Mon, 18 Apr 2022 11:10:30 -0700
Tony Nguyen <anthony.l.nguyen@intel.com> wrote:

> > If you want to leave the code as is and remove this from the patch
> > let me know and I will send v2.  
> 
> The change itself looks ok to me, but for net patches, we should fix the 
> issue without introducing other changes. A v2 without this change would 
> be great; feel free to submit this change to -next after I've applied 
> the v2 for this patch.
> 
> Thanks,
> 
> Tony
Agree, sending v2.

Thanks,
Ivan


  reply	other threads:[~2022-04-19 14:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  7:22 [Intel-wired-lan] [PATCH net] ice: Protect vf_state check by cfg_lock in ice_vc_process_vf_msg() Ivan Vecera
2022-04-13  7:22 ` Ivan Vecera
2022-04-15 11:55 ` [Intel-wired-lan] " Maciej Fijalkowski
2022-04-15 11:55   ` Maciej Fijalkowski
2022-04-15 11:57   ` Maciej Fijalkowski
2022-04-15 11:57     ` Maciej Fijalkowski
2022-04-15 13:53     ` Alexander Lobakin
2022-04-15 13:53       ` Alexander Lobakin
2022-04-15 20:55     ` Tony Nguyen
2022-04-15 20:55       ` Tony Nguyen
2022-04-16 11:30       ` Ivan Vecera
2022-04-16 11:30         ` Ivan Vecera
2022-04-18 18:10         ` Tony Nguyen
2022-04-18 18:10           ` Tony Nguyen
2022-04-19 14:23           ` Ivan Vecera [this message]
2022-04-19 14:23             ` Ivan Vecera
2022-04-15 16:38   ` Ivan Vecera
2022-04-15 16:38     ` Ivan Vecera
2022-04-15 18:31     ` Keller, Jacob E
2022-04-15 18:31       ` Keller, Jacob E
2022-04-15 20:53       ` Tony Nguyen
2022-04-15 20:53         ` Tony Nguyen

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=20220419162302.60378ede@ceranb \
    --to=ivecera@redhat.com \
    --cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.