linux-kernel - Re: [PATCH v2 2/3] alarmtimer: Use wakeup source from alarmtimer platform device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAD=FV=XLK8g67O_dfPXVd0JxQY4_srwghmyA0bzy6fZPuTdHhg@mail.gmail.com>
Date:   Tue, 21 Jan 2020 15:45:03 -0800
From:   Doug Anderson <dianders@...omium.org>
To:     Stephen Boyd <swboyd@...omium.org>
Cc:     John Stultz <john.stultz@...aro.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        LKML <linux-kernel@...r.kernel.org>,
        Stephen Boyd <sboyd@...nel.org>
Subject: Re: [PATCH v2 2/3] alarmtimer: Use wakeup source from alarmtimer
 platform device

Hi,

On Tue, Jan 21, 2020 at 11:48 AM Stephen Boyd <swboyd@...omium.org> wrote:
>
> Use the wakeup source that can be associated with the 'alarmtimer'
> platform device instead of registering another one by hand.
>
> Signed-off-by: Stephen Boyd <swboyd@...omium.org>
> ---
>  kernel/time/alarmtimer.c | 15 +++++----------
>  1 file changed, 5 insertions(+), 10 deletions(-)

Seems like a good idea to me.  With the same caveat that I'm no expert
in this part of the code:

Reviewed-by: Douglas Anderson <dianders@...omium.org>