linux-kernel - Re: [PATCH v3 19/47] mfd: rk808: Register power-off handler with kernel power-off handler

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: <20141103190602.GE10558@roeck-us.net>
Date:	Mon, 3 Nov 2014 11:06:02 -0800
From:	Guenter Roeck <linux@...ck-us.net>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
	Chris Zhong <zyw@...k-chips.com>,
	Zhang Qing <zhangqing@...k-chips.com>,
	Samuel Ortiz <sameo@...ux.intel.com>
Subject: Re: [PATCH v3 19/47] mfd: rk808: Register power-off handler with
 kernel power-off handler

On Mon, Nov 03, 2014 at 05:53:46PM +0000, Lee Jones wrote:
> On Mon, 27 Oct 2014, Guenter Roeck wrote:
> 
> > Register with kernel power-off handler instead of setting pm_power_off
> > directly. Register with low priority to reflect that the original code
> > only sets pm_power_off if it was not already set.
> > 
> > Cc: Chris Zhong <zyw@...k-chips.com>
> > Cc: Zhang Qing <zhangqing@...k-chips.com>
> > Signed-off-by: Guenter Roeck <linux@...ck-us.net>
> > ---
> > v3:
> > - Replace poweroff in all newly introduced variables and in text
> >   with power_off or power-off as appropriate
> > - Replace POWEROFF_PRIORITY_xxx with POWER_OFF_PRIORITY_xxx
> > v2:
> > - New patch
> > 
> >  drivers/mfd/rk808.c       | 30 ++++++++++++++++--------------
> >  include/linux/mfd/rk808.h |  2 ++
> >  2 files changed, 18 insertions(+), 14 deletions(-)
> 
> Code looks okay:
> 
> Acked-by: Lee Jones <lee.jones@...aro.org>
> 
Thanks!

> ... but how are you thinking about handling this set?
> 

Plan is to send the entire series directly to Linus in the next
commit window, as suggested by several of the affected maintainers.

I am still missing an Ack for patch 1 of the series. If/when I get
that, I'll set up the series except for the last patch to be added
to linux-next for it to get some exposure.

Of course, that plan may all fall apart if someone objects. In that case,
the patches would have to be taken over several releases by the individual
maintainers.

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