From: Joe Damato <joe@dama.to>
To: Yuesong Li <liyuesong@vivo.com>
Cc: Taehee Yoo <ap420073@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
opensource.kernel@vivo.com
Subject: Re: [PATCH net-next v1] net: amt: convert to use secs_to_jiffies
Date: Fri, 13 Jun 2025 15:07:35 +0300 [thread overview]
Message-ID: <aEwUh3A3gvj64v0a@MacBook-Air.local> (raw)
In-Reply-To: <20250613102014.3070898-1-liyuesong@vivo.com>
On Fri, Jun 13, 2025 at 06:20:12PM +0800, Yuesong Li wrote:
> Since secs_to_jiffies()(commit:b35108a51cf7) has been introduced, we can
> use it to avoid scaling the time to msec.
>
> Signed-off-by: Yuesong Li <liyuesong@vivo.com>
> ---
> drivers/net/amt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/amt.c b/drivers/net/amt.c
> index 734a0b3242a9..fb130fde68c0 100644
> --- a/drivers/net/amt.c
> +++ b/drivers/net/amt.c
> @@ -979,7 +979,7 @@ static void amt_event_send_request(struct amt_dev *amt)
> amt->req_cnt++;
> out:
> exp = min_t(u32, (1 * (1 << amt->req_cnt)), AMT_MAX_REQ_TIMEOUT);
> - mod_delayed_work(amt_wq, &amt->req_wq, msecs_to_jiffies(exp * 1000));
> + mod_delayed_work(amt_wq, &amt->req_wq, secs_to_jiffies(exp));
> }
>
> static void amt_req_work(struct work_struct *work)
Seems fine, but minor nit on the commit message -- when referring to commit
you should include the one-liner as per the documentation [1].
For example, maybe something like:
Since commit b35108a51cf7 ("jiffies: Define secs_to_jiffies()"), ...
Otherwise:
Reviewed-by: Joe Damato <joe@dama.to>
[1]: https://www.kernel.org/doc/html/v6.15/process/submitting-patches.html
next prev parent reply other threads:[~2025-06-13 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 10:20 [PATCH net-next v1] net: amt: convert to use secs_to_jiffies Yuesong Li
2025-06-13 12:07 ` Joe Damato [this message]
2025-06-14 2:27 ` Taehee Yoo
2025-06-14 18:30 ` patchwork-bot+netdevbpf
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=aEwUh3A3gvj64v0a@MacBook-Air.local \
--to=joe@dama.to \
--cc=andrew+netdev@lunn.ch \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liyuesong@vivo.com \
--cc=netdev@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=pabeni@redhat.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