From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Anna-Maria Behnsen <anna-maria@linutronix.de>,
lkp@intel.com, Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:BLUETOOTH SUBSYSTEM" <linux-bluetooth@vger.kernel.org>
Cc: eahariha@linux.microsoft.com,
Naman Jain <namjain@linux.microsoft.com>,
Michael Kelley <mhklinux@outlook.com>
Subject: Re: [PATCH 1/2] jiffies: Define secs_to_jiffies()
Date: Wed, 23 Oct 2024 11:02:00 -0700 [thread overview]
Message-ID: <e7a96b43-6d01-49ae-ad0d-4cb75ea69822@linux.microsoft.com> (raw)
In-Reply-To: <8734kngfni.fsf@somnus>
On 10/23/2024 5:36 AM, Anna-Maria Behnsen wrote:
> Easwar Hariharan <eahariha@linux.microsoft.com> writes:
>
>> There are ~500 usages of msecs_to_jiffies() that either use a multiplier
>> value of 1000 or equivalently MSEC_PER_SEC. Define secs_to_jiffies() to
>> allow such code to be less clunky.
>
> Can you please provide a proper cover letter for a series (also if it is
> a series with only 2 patches)?
Yes, apologies, this isn't my usual mode of operations.
>
> Regarding your commit message: secs_to_jiffies() is defined in hci_event
> and cannot be reused by other callsites and this is why it's valuable to
> move it into core code. Especially because there are ~500 users which do
> the multiplier thing and there are also several users which use (secs *
> HZ).
>
> What do you think about converting the other users e.g. using
> Coccinelle?
>
I intended to follow up this series with such. I'm not super familiar
with Coccinelle and am occupied by commercial work, so that may take longer.
>> Suggested-by: Michael Kelley <mhklinux@outlook.com>
>> Signed-off-by: Easwar Hariharan <eahariha@linux.microsoft.com>
>> ---
>> include/linux/jiffies.h | 2 ++
>> net/bluetooth/hci_event.c | 2 --
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/include/linux/jiffies.h b/include/linux/jiffies.h
>> index 1220f0fbe5bf..50dba516fd2f 100644
>> --- a/include/linux/jiffies.h
>> +++ b/include/linux/jiffies.h
>> @@ -526,6 +526,8 @@ static __always_inline unsigned long msecs_to_jiffies(const unsigned int m)
>> }
>> }
>>
>> +#define secs_to_jiffies(_secs) msecs_to_jiffies((_secs) * MSEC_PER_SEC)
>> +
>
> Why not only doing
>
> #define secs_to_jiffies(s) (s * HZ)
Yes, fair enough, I can change accordingly.
Thanks,
Easwar
next prev parent reply other threads:[~2024-10-23 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 18:53 Easwar Hariharan
2024-10-22 18:53 ` [PATCH 2/2] drivers: hv: Convert open-coded timeouts to secs_to_jiffies() Easwar Hariharan
2024-10-22 22:58 ` Easwar Hariharan
2024-10-23 5:36 ` Praveen Kumar
2024-10-23 17:35 ` Easwar Hariharan
2024-10-22 22:58 ` [PATCH 1/2] jiffies: Define secs_to_jiffies() Easwar Hariharan
2024-10-23 12:36 ` Anna-Maria Behnsen
2024-10-23 18:02 ` Easwar Hariharan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-22 18:52 Easwar Hariharan
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=e7a96b43-6d01-49ae-ad0d-4cb75ea69822@linux.microsoft.com \
--to=eahariha@linux.microsoft.com \
--cc=anna-maria@linutronix.de \
--cc=geert@linux-m68k.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mhklinux@outlook.com \
--cc=namjain@linux.microsoft.com \
--cc=tglx@linutronix.de \
/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®