linux-kernel - Re: [PATCH 2/3] clocksource: dbx500: convert to clocksource_register

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: <1322854083.21423.168.camel@work-vm>
Date:	Fri, 02 Dec 2011 11:28:03 -0800
From:	John Stultz <john.stultz@...aro.org>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Yong Zhang <yong.zhang0@...il.com>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Mattias Wallin <mattias.wallin@...ricsson.com>
Subject: Re: [PATCH 2/3] clocksource: dbx500: convert to
 clocksource_register_hz()

On Fri, 2011-12-02 at 09:29 +0100, Linus Walleij wrote:
> On Fri, Dec 2, 2011 at 12:55 AM, John Stultz <john.stultz@...aro.org> wrote:
> > On Thu, 2011-12-01 at 15:20 +0800, Yong Zhang wrote:
> >> Convert clocksource_dbx500_prcmu to use clocksource_register_hz.
> 
> > I've queued this myself, but I'd prefer it to go through the appropriate
> > maintainer. That said, if I don't see it in -next in a week or so, I'll
> > go ahead and add it to my 3.3 list for Thomas.
> 
> Given that the driver is in drivers/clocksource/* aren't You+Thomas
> the maintainers?

Fair enough. :) 

I just want to make sure I'm not breaking anything, or surprising
anyone, since I've got limited ability to test all the various hardware
drivers.

> Actually this is one of the instances where we try to push ARM stuff
> down to a subsystem where it belongs for proper handling by the
> subsystem maintainers.

Alrighty, as long as I get an ack or tested-by from someone who has
hardware this sounds reasonable. 

thanks!
-john


--
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/