From: Karthik Sundaravel <ksundara@redhat.com>
To: jesse.brandeburg@intel.com, wojciech.drewek@intel.com,
sumang@marvell.com, jacob.e.keller@intel.com,
anthony.l.nguyen@intel.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, horms@kernel.org
Cc: pmenzel@molgen.mpg.de, aharivel@redhat.com, jiri@resnulli.us,
cfontain@redhat.com, vchundur@redhat.com, ksundara@redhat.com,
michal.swiatkowski@linux.intel.com, rjarry@redhat.com
Subject: [Intel-wired-lan] [PATCH iwl-next v9] ice: Add get/set hw address for VFs using devlink commands
Date: Wed, 15 May 2024 19:52:06 +0530 [thread overview]
Message-ID: <20240515142207.27369-1-ksundara@redhat.com> (raw)
Dear Maintainers,
Thanks for the review and suggestions for my patch.
v8 -> v9
--------
- Rebasing against dev-queue branch of next-queue tree
v7 -> v8
--------
- Added const keyword for the parameter ``mac`` in ice_set_vf_fn_mac()
v6 -> v7
--------
- Addressed Smatch and checkpatch issues
v5 -> v6
--------
- Changed data type of vf_id to u16
- Used container_of(port, struct ice_vf, devlink_port) to
get the vf instead of ice_get_vf_by_id()/ice_put_vf()
v4 -> v5
--------
- Cloned ice_set_vf_mac() to ice_set_vf_fn_mac() so that the
parameter ice_pf is used instead of net_device of vf
- removed redundant error handling
v3 -> v4
--------
- Released the vf device by calling ice_put_vf()
v2 -> v3
--------
- Fill the extack message instead of dev_err()
v1 -> v2
--------
- called ice_set_vf_mac() directly from the devlink port function
handlers.
RFC -> v1
---------
- Add the function handlers to set and get the HW address for the
VF representor ports.
next reply other threads:[~2024-05-15 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 14:22 Karthik Sundaravel [this message]
2024-05-15 14:22 ` [Intel-wired-lan] [PATCH iwl-next v9] ice: Add get/set hw address for VFs using devlink commands Karthik Sundaravel
2024-05-15 16:52 ` Brett Creeley
2024-05-15 21:21 ` Keller, Jacob E
2024-05-16 15:01 ` Brett Creeley
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=20240515142207.27369-1-ksundara@redhat.com \
--to=ksundara@redhat.com \
--cc=aharivel@redhat.com \
--cc=anthony.l.nguyen@intel.com \
--cc=cfontain@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=rjarry@redhat.com \
--cc=sumang@marvell.com \
--cc=vchundur@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).