From: David Miller <davem@davemloft.net>
To: weifeng.voon@intel.com
Cc: mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, joabreu@synopsys.com,
peppe.cavallaro@st.com, andrew@lunn.ch, alexandre.torgue@st.com,
boon.leong.ong@intel.com, chen.yong.seow@intel.com,
mgross@linux.intel.com, vee.khee.wong@intel.com
Subject: Re: [PATCH v1 net] net: stmmac: Modify configuration method of EEE timers
Date: Mon, 28 Sep 2020 12:34:02 -0700 (PDT) [thread overview]
Message-ID: <20200928.123402.281706664300059159.davem@davemloft.net> (raw)
In-Reply-To: <20200928100241.7673-1-weifeng.voon@intel.com>
From: Voon Weifeng <weifeng.voon@intel.com>
Date: Mon, 28 Sep 2020 18:02:41 +0800
> @@ -90,11 +90,12 @@ static const u32 default_msg_level = (NETIF_MSG_DRV | NETIF_MSG_PROBE |
> NETIF_MSG_LINK | NETIF_MSG_IFUP |
> NETIF_MSG_IFDOWN | NETIF_MSG_TIMER);
>
> -#define STMMAC_DEFAULT_LPI_TIMER 1000
> -static int eee_timer = STMMAC_DEFAULT_LPI_TIMER;
> -module_param(eee_timer, int, 0644);
> -MODULE_PARM_DESC(eee_timer, "LPI tx expiration time in msec");
> -#define STMMAC_LPI_T(x) (jiffies + msecs_to_jiffies(x))
> +#define STMMAC_DEFAULT_LPI_TIMER 1000000
> +#define STMMAC_LPI_T(x) (jiffies + usecs_to_jiffies(x))
> +
> +static int tw_timer = STMMAC_DEFAULT_TWT_LS;
> +module_param(tw_timer, int, 0644);
> +MODULE_PARM_DESC(tw_timer, "LPI TW timer value in msec");
This is a great example of one of the many reasons why we disallow
module parameters in networking drivers.
This is a user facing value, and now you changed the name which breaks
things for anyone who was accessing this module parameter previously.
You have to find a way to specify this value using existing kernel
infrastructure such as ethtool or devlink, and not using a module
parameter.
So please get rid of this module parameter, and add a way to set this
value portably.
prev parent reply other threads:[~2020-09-28 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 10:02 Voon Weifeng
2020-09-28 19:34 ` David Miller [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=20200928.123402.281706664300059159.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexandre.torgue@st.com \
--cc=andrew@lunn.ch \
--cc=boon.leong.ong@intel.com \
--cc=chen.yong.seow@intel.com \
--cc=joabreu@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mgross@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=vee.khee.wong@intel.com \
--cc=weifeng.voon@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
all inboxes | Powered by JetHome®