From: Simon Horman <horms@kernel.org>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
jacob.e.keller@intel.com, michal.kubiak@intel.com,
maciej.fijalkowski@intel.com, sridhar.samudrala@intel.com,
przemyslaw.kitszel@intel.com, wojciech.drewek@intel.com,
pio.raczynski@gmail.com, jiri@nvidia.com,
mateusz.polchlopek@intel.com, shayd@nvidia.com, kuba@kernel.org
Subject: Re: [iwl-next v3 2/4] ice: move devlink locking outside the port creation
Date: Fri, 14 Jun 2024 13:48:06 +0100 [thread overview]
Message-ID: <20240614124806.GO8447@kernel.org> (raw)
In-Reply-To: <20240610074434.1962735-3-michal.swiatkowski@linux.intel.com>
On Mon, Jun 10, 2024 at 09:44:32AM +0200, Michal Swiatkowski wrote:
> In case of subfunction lock will be taken for whole port creation and
> removing. Do the same in VF case.
>
> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-06-14 12:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 7:44 [iwl-next v3 0/4] ice: prepare representor for SF support Michal Swiatkowski
2024-06-10 7:44 ` [iwl-next v3 1/4] ice: store representor ID in bridge port Michal Swiatkowski
2024-06-14 12:43 ` Simon Horman
2024-06-10 7:44 ` [iwl-next v3 2/4] ice: move devlink locking outside the port creation Michal Swiatkowski
2024-06-14 12:48 ` Simon Horman [this message]
2024-06-10 7:44 ` [iwl-next v3 3/4] ice: move VSI configuration outside repr setup Michal Swiatkowski
2024-06-14 12:43 ` Simon Horman
2024-06-21 4:16 ` Michal Swiatkowski
2024-06-10 7:44 ` [iwl-next v3 4/4] ice: update representor when VSI is ready Michal Swiatkowski
2024-06-14 12:47 ` Simon Horman
2024-06-21 4:32 ` Michal Swiatkowski
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=20240614124806.GO8447@kernel.org \
--to=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=mateusz.polchlopek@intel.com \
--cc=michal.kubiak@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pio.raczynski@gmail.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=shayd@nvidia.com \
--cc=sridhar.samudrala@intel.com \
--cc=wojciech.drewek@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;
as well as URLs for NNTP newsgroup(s).