[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6DD008D392@AcuExch.aculab.com>
Date: Mon, 9 Oct 2017 09:15:17 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Kees Cook' <keescook@...omium.org>,
Paul Bolle <pebolle@...cali.nl>
CC: Karsten Keil <isdn@...ux-pingi.de>,
"David S. Miller" <davem@...emloft.net>,
Johan Hovold <johan@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
"gigaset307x-common@...ts.sourceforge.net"
<gigaset307x-common@...ts.sourceforge.net>,
Network Development <netdev@...r.kernel.org>
Subject: RE: [PATCH v2] isdn/gigaset: Convert timers to use timer_setup()
From: Kees Cook
> Sent: 06 October 2017 20:40
...
> I'm in no rush for any specific change. There are about 900 call sites
> I'm making my way through, about 2/3rd are pretty trivial, and the
> less obvious is what I've started sending out now, since I expect some
> will need some more careful review.
Is it worth adding a structure that contains a timer and an extra 'long'
than can be used to maintain the existing API logic for the 'difficult'
cases?
David
Powered by blists - more mailing lists