linux-kernel - Re: [PATCH 0/4] Android Alarm Driver Cleanups (for staging-next/3.5)

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: <20120420220849.GA5642@kroah.com>
Date:	Fri, 20 Apr 2012 15:08:49 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	John Stultz <john.stultz@...aro.org>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Colin Cross <ccross@...roid.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Android Kernel Team <kernel-team@...roid.com>
Subject: Re: [PATCH 0/4] Android Alarm Driver Cleanups (for staging-next/3.5)

On Fri, Apr 20, 2012 at 12:31:43PM -0700, John Stultz wrote:
> This patch-set moves the Android alarm driver in staging to use
> the upstreamed CLOCK_BOOTTIME and alarmtimer interfaces, allowing
> us to greatly shrink the alarm driver.
> 
> The Google Android team has been using these patches in its AOSP tree
> for a little while without any reported issues.
> 
> The only gotcha is that I needed to make one alarmtimer interface
> non-static in order to support the android alarm driver. This sort
> of is a grey area for the staging tree, but I'm the author of the
> upstreamed alarmtimer code, and Thomas (cc'ed) had no objection
> to this patch going in via the staging tree, instead of -tip so 
> this should be ok (and much simpler then dealing with
> cross-maintainer dependencies).
> 
> Greg: Would you mind applying this set to staging-next for 3.5?

It took some messing with (due to some over-eager people fixing spelling
mistakes and compiler warnings that you didn't have in your tree), but
I've applied these now.  Thanks for doing this work.

But, as I already said, this patch set produces some big compiler
warnings, can you please fix them up before I get nasty messages from
the linux-next maintainer?

thanks,

greg k-h
--
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/