linux-kernel - Re: [RFC PATCH] ARM: clocksource: make ARM_GLOBAL

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: <20160226152714.GD3173@xsjsorenbubuntu>
Date:	Fri, 26 Feb 2016 07:27:14 -0800
From:	Sören Brinkmann <soren.brinkmann@...inx.com>
To:	Grygorii Strashko <grygorii.strashko@...com>
CC:	Moritz Fischer <moritz.fischer@...us.com>, <kernel@...inux.com>,
	<tony@...mide.com>, <nsekhar@...com>,
	Masahiro Yamada <yamada.masahiro@...ionext.com>,
	Florian Fainelli <f.fainelli@...il.com>,
	Russell King <linux@....linux.org.uk>,
	Daniel Lezcano <daniel.lezcano@...aro.org>,
	Michal Simek <michal.simek@...inx.com>,
	Wei Xu <xuwei5@...ilicon.com>,
	<linux-rockchip@...ts.infradead.org>,
	<bcm-kernel-feedback-list@...adcom.com>,
	Arnd Bergmann <arnd@...db.de>,
	"Liviu Dudau" <liviu.dudau@....com>, <linux-omap@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	Maxime Coquelin <maxime.coquelin@...com>,
	Srinivas Kandagatla <srinivas.kandagatla@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Sascha Hauer <kernel@...gutronix.de>,
	"Sudeep Holla" <sudeep.holla@....com>,
	Olof Johansson <olof@...om.net>, Jun Nie <jun.nie@...aro.org>,
	Shawn Guo <shawnguo@...nel.org>
Subject: Re: [RFC PATCH] ARM: clocksource: make ARM_GLOBAL_TIMER selectable

On Fri, 2016-02-26 at 15:03:19 +0200, Grygorii Strashko wrote:
> On 02/05/2016 01:39 AM, Sören Brinkmann wrote:
> > On Thu, 2016-02-04 at 15:14:47 -0800, Moritz Fischer wrote:
> >> Hi Soeren,
> >>
> >> On Thu, Feb 4, 2016 at 2:41 PM, Sören Brinkmann
> >> <soren.brinkmann@...inx.com> wrote:
> >>
> >>> But with this change the 'if !CPU_FREQ' becomes obsolete.
> >> I'm confused, could you explain that statement? You don't want people
> >> accidentally running with GT when CPU_FREQ is on, right?
> > 
> > Correct. But with this Kconfig rework you can just deselect it in
> > Kconfig. The generic HAVE_GT could always be selected.
> > 
> 
> 
> Don't know whom should i ask - but what will be the final conclusion here?
> Can it be merged?

I think we don't break anything either way. Would just be some
additional clean up to get rid of that mentioned constraint (which
doesn't really work well anyway in the multi-arch kernel). So, no real
objections to merging it from my side.

	Thanks,
	Sören