linux-kernel - Re: [PATCH] [RFC] android-alarm: Switch from wakelocks to wakeup sources

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] [day] [month] [year] [list]

Message-ID: <CAMP5XgcHg+haaYz+zamu+ue+rOPNgBg0zdMZvyim+pDGAEBnLQ@mail.gmail.com>
Date:	Fri, 20 Apr 2012 18:05:51 -0700
From:	Arve Hjønnevåg <arve@...roid.com>
To:	John Stultz <john.stultz@...aro.org>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Colin Cross <ccross@...roid.com>,
	Greg KH <gregkh@...uxfoundation.org>,
	Android Kernel Team <kernel-team@...roid.com>
Subject: Re: [PATCH] [RFC] android-alarm: Switch from wakelocks to wakeup sources

On Fri, Apr 20, 2012 at 5:23 PM, John Stultz <john.stultz@...aro.org> wrote:
> In their current AOSP tree, the Android in-kernel wakelock
> infrastructure has been reimplemented in terms of wakeup
> sources:
> http://git.linaro.org/gitweb?p=people/jstultz/android.git;a=commitdiff;h=e9911f4efdc55af703b8b3bb8c839e6f5dd173bb
>
> The Android alarm driver currently has stubbed out calls
> to wakelock functionality. So this patch simply converts
> the stubbed out wakelock calls to wakeup source calls, and
> removes the empty wakelock macros
>
> This is something I'd like to propose for staging, but wanted
> to get some input from Arve, Colin or other member of the
> Android team first.
>
> Thoughts or objections?
>

Looks reasonable to me.

-- 
Arve Hjønnevåg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/