From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Fabien R <theedge456@free.fr>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: timer API change from kernel 4.9 to 5.0
Date: Wed, 30 Sep 2020 14:48:41 -0400 [thread overview]
Message-ID: <76270.1601491721@turing-police> (raw)
In-Reply-To: <b3797868-7ce7-5135-f532-8fc86d121a68@free.fr>
[-- Attachment #1.1: Type: text/plain, Size: 885 bytes --]
On Wed, 30 Sep 2020 18:34:07 +0200, Fabien R said:
> Hello,
> In timer.h of 4.9, struct timer_list contains a field data which is unsigned long.
> In timer.c, call_timer_fn calls the triggered function with data as parameter.
> As of 5.0, the field data disappears from struct timer_list and call_timer_fn
> is used with a struct timer_list * as parameter.
> Is there some info about this change somewhere ?
[/usr/src/linux-next] git log v4.9..v5.0 -- kernel/time/timer.c
and reading through finds this:
commit 354b46b1a0adda1dd5b7f0bc2a5604cca091be5f
Author: Kees Cook <keescook@chromium.org>
Date: Sun Oct 22 19:15:40 2017 -0700
timer: Switch callback prototype to take struct timer_list * argument
Since all callbacks have been converted, we can switch the core
prototype to "struct timer_list *" now too.
(and several other commits from Kees following that)
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-09-30 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 16:34 timer API change from kernel 4.9 to 5.0 Fabien R
2020-09-30 18:04 ` Greg KH
2020-09-30 18:48 ` Valdis Klētnieks [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=76270.1601491721@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=theedge456@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).