[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171019193346.GE1978@nanopsycho.orion>
Date: Thu, 19 Oct 2017 21:33:46 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Steve Lin <steven.lin1@...adcom.com>
Cc: netdev@...r.kernel.org, jiri@...lanox.com, davem@...emloft.net,
michael.chan@...adcom.com, linville@...driver.com,
gospo@...adcom.com
Subject: Re: [PATCH net-next v2 2/6] devlink: Adding SR-IOV enablement NVRAM
config param
Thu, Oct 19, 2017 at 09:17:06PM CEST, steven.lin1@...adcom.com wrote:
>Adding DEVLINK_PERM_CONFIG_SRIOV_ENABLED permanent config
>parameter. If value is 1, SR-IOV is enabled. If value is 0,
>SR-IOV is disabled on this device. Value is permanent (stored
>in NVRAM), so becomes the new default value for this device.
>
>Signed-off-by: Steve Lin <steven.lin1@...adcom.com>
>Acked-by: Andy Gospodarek <gospo@...adcom.com>
>---
> include/uapi/linux/devlink.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
>diff --git a/include/uapi/linux/devlink.h b/include/uapi/linux/devlink.h
>index 47cc584..2640203 100644
>--- a/include/uapi/linux/devlink.h
>+++ b/include/uapi/linux/devlink.h
>@@ -255,4 +255,9 @@ enum devlink_dpipe_header_id {
> DEVLINK_DPIPE_HEADER_IPV6,
> };
>
>+/* Permanent (NVRAM) config parameters */
We need the decription here in the header as well. Commit message alone
is no good for this.
Also, there should not be mention of "NVRAM". It is up to the device
implementation where is stores the value.
>+enum devlink_perm_config_param {
>+ DEVLINK_PERM_CONFIG_SRIOV_ENABLED,
>+};
>+
> #endif /* _UAPI_LINUX_DEVLINK_H_ */
>--
>2.7.4
>
Powered by blists - more mailing lists