[<prev] [next>] [day] [month] [year] [list]
Date: Tue, 10 Oct 2017 07:22:05 -0700
From: Kees Cook <keescook@...omium.org>
To: Kalle Valo <kvalo@...eaurora.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
linux-wireless <linux-wireless@...r.kernel.org>,
Network Development <netdev@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: net/wireless/ray_cs: Convert timers to use
On Tue, Oct 10, 2017 at 1:26 AM, Kalle Valo <kvalo@...eaurora.org> wrote:
> Kees Cook <keescook@...omium.org> wrote:
>
>> In preparation for unconditionally passing the struct timer_list pointer to
>> all timer callbacks, switch to using the new timer_setup() and from_timer()
>> to pass the timer pointer explicitly.
>>
>> Cc: Kalle Valo <kvalo@...eaurora.org>
>> Cc: linux-wireless@...r.kernel.org
>> Cc: netdev@...r.kernel.org
>> Cc: Thomas Gleixner <tglx@...utronix.de>
>> Signed-off-by: Kees Cook <keescook@...omium.org>
>
> I'll apply this once I have fast forwarded wireless-drivers-next to
> -rc3. I'll also fix the title, what was it supposed to say?
It was truncated from "net/wireless/ray_cs: Convert timers to use
timer_setup()"; I've fixed that glitch in my workflow now.
> Patch set to Awaiting Upstream.
Thanks!
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists