From: Christian Marangi <ansuelsmth@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Vladimir Oltean <olteanv@gmail.com>,
"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
Subject: Re: [PATCH net-next] net: dsa: qca8k: Fix inconsistent use of jiffies vs milliseconds
Date: Mon, 16 Dec 2024 20:55:13 +0100 [thread overview]
Message-ID: <676085a7.050a0220.1e6031.2193@mx.google.com> (raw)
In-Reply-To: <87195b12-6dfa-4778-b0c0-39f3a64a399e@lunn.ch>
On Mon, Dec 16, 2024 at 10:21:12AM +0100, Andrew Lunn wrote:
> On Mon, Dec 16, 2024 at 01:13:34AM +0200, Vladimir Oltean wrote:
> > On Sun, Dec 15, 2024 at 05:43:55PM +0000, Andrew Lunn wrote:
> > > wait_for_complete_timeout() expects a timeout in jiffies. With the
> > > driver, some call sites converted QCA8K_ETHERNET_TIMEOUT to jiffies,
> > > others did not. Make the code consistent by changes the #define to
> > > include a call to msecs_to_jiffies, and remove all other calls to
> > > msecs_to_jiffies.
> > >
> > > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> > > ---
> >
> > If my calculations are correct, for CONFIG_HZ=100, 5 jiffies last 50 ms.
> > So, assuming that configuration, the patch would be _decreasing_ the timeout
> > from 50 ms to 5 ms. The change should be tested to confirm it's enough.
> > Christian, could you do that?
>
> I've have an qca8k system now, and have tested this patch. However, a
> Tested-by: from Christian would be very welcome.
>
Hi need 1-2 days to test this, hope that is O.K.
--
Ansuel
next prev parent reply other threads:[~2024-12-16 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 17:43 [PATCH net-next] net: dsa: qca8k: Fix inconsistent use of jiffies vs milliseconds Andrew Lunn
2024-12-15 23:13 ` Vladimir Oltean
2024-12-16 9:21 ` Andrew Lunn
2024-12-16 19:55 ` Christian Marangi [this message]
2024-12-16 23:08 ` Andrew Lunn
2024-12-18 12:50 ` 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=676085a7.050a0220.1e6031.2193@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.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