linux-kernel - Re: [PATCH V2 1/7] clockevents: Allow set-state callbacks to be optional

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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.DEB.2.11.1506291114180.4037@nanos>
Date:	Mon, 29 Jun 2015 11:15:23 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Daniel Lezcano <daniel.lezcano@...aro.org>
cc:	Viresh Kumar <viresh.kumar@...aro.org>,
	linaro-kernel@...ts.linaro.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 1/7] clockevents: Allow set-state callbacks to be
 optional

On Mon, 29 Jun 2015, Daniel Lezcano wrote:

> On 06/12/2015 10:00 AM, Viresh Kumar wrote:
> > Its mandatory for the drivers to provide set_state_{oneshot|periodic}()
> > (only if related modes are supported) and set_state_shutdown() callbacks
> > today, if they are implementing the new set-state interface.
> > 
> > But this leads to unnecessary noop callbacks for drivers which don't
> > want to implement them. Over that, it will lead to a full function call
> > for nothing really useful.
> > 
> > Lets make all set-state callbacks optional.
> > 
> > Suggested-by: Daniel Lezcano <daniel.lezcano@...aro.org>
> > Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> 
> As this patch is needed for the other changes in this patchset, is it possible
> to take it through my tree Thomas ?

I have not other dependencies in that area ATM, so it can bake in
yours and I'll pull it over then.

Thanks,

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