From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: <ovidiu.panait@windriver.com>, <intel-wired-lan@lists.osuosl.org>
Cc: slawomirx.mrozowicz@intel.com, anthony.l.nguyen@intel.com,
jesse.brandeburg@intel.com
Subject: Re: [Intel-wired-lan] [PATCH] ixgbe: report link state for VF devices
Date: Fri, 8 Dec 2023 11:44:09 +0100 [thread overview]
Message-ID: <a2ac9348-8bd9-c9ec-59cf-38f24b8a304d@intel.com> (raw)
In-Reply-To: <20231208100349.2199641-1-ovidiu.panait@windriver.com>
On 12/8/23 11:03, ovidiu.panait@windriver.com wrote:
> From: Ovidiu Panait <ovidiu.panait@windriver.com>
>
> The link state of VF devices can be controlled via "ip link set", but the
> current state (auto/disabled) is not reported by "ip link show".
>
> Update ixgbe_ndo_get_vf_config() to make this info available to userspace.
>
> Fixes: 366fd1000995 ("ixgbe: add the ability for the PF to disable VF link state")
I would say that your commit extends ixgbe functionality, and is not a
bugfix. For such cases you should avoid Fixes: tag (just mentioning
commit "that introduced the code/ndo" is fine). With that, you could
also specify the tree as "iwl-next", what will also clarify that you
want Intel VAL to process this patch prior to application.
> Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c
> index 9cfdfa8a4355..21b18d2f0d55 100644
> --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c
> +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c
> @@ -1849,5 +1849,6 @@ int ixgbe_ndo_get_vf_config(struct net_device *netdev,
> ivi->spoofchk = adapter->vfinfo[vf].spoofchk_enabled;
> ivi->rss_query_en = adapter->vfinfo[vf].rss_query_enabled;
> ivi->trusted = adapter->vfinfo[vf].trusted;
> + ivi->linkstate = adapter->vfinfo[vf].link_state;
> return 0;
> }
code looks fine,
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2023-12-08 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 10:03 [Intel-wired-lan] [PATCH] ixgbe: report link state for VF devices ovidiu.panait
2023-12-08 10:44 ` Przemek Kitszel [this message]
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=a2ac9348-8bd9-c9ec-59cf-38f24b8a304d@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=ovidiu.panait@windriver.com \
--cc=slawomirx.mrozowicz@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