linux-kernel - Re: [PATCH v8 0/7] power management patch set

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: <B848F8F1-8FBC-46D8-B8FB-002077482E92@kernel.crashing.org>
Date:	Fri, 27 Jul 2012 16:28:00 -0500
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Li Yang <leoli@...escale.com>
Cc:	Zhao Chenhui <chenhui.zhao@...escale.com>, scottwood@...escale.com,
	linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 0/7] power management patch set


On Jul 26, 2012, at 10:14 PM, Li Yang wrote:

> On Fri, Jul 27, 2012 at 1:29 AM, Kumar Gala <galak@...nel.crashing.org> wrote:
>> 
>> On Jul 26, 2012, at 9:02 AM, Li Yang wrote:
>> 
>>> On Fri, Jul 20, 2012 at 8:42 PM, Zhao Chenhui
>>> <chenhui.zhao@...escale.com> wrote:
>>>> Changes for v8:
>>>> * Separated the cpu hotplug patch into three patches, as follows
>>>> [PATCH v8 1/7] powerpc/smp: use a struct epapr_spin_table to replace macros
>>>> [PATCH v8 2/7] powerpc/smp: add generic_set_cpu_up() to set cpu_state as CPU_UP_PREPARE
>>>> [PATCH v8 4/7] powerpc/85xx: add HOTPLUG_CPU support
>>>> 
>>>> * Replaced magic numbers with macros in "[PATCH 5/7] powerpc/85xx: add sleep and deep sleep support"
>>>> 
>>>> * no change to the rest of the patch set
>>> 
>>> Hi Kumar,
>>> 
>>> How about picking about this series for 3.6?  The review seems to
>>> settle down for this revision.
>> 
>> Its too late for 3.6, but will look at queuing it up for 3.7.
> 
> Too late?  The latest version were submitted on Jul 20 and you are
> still picking up other patches today.  :)  I do think the patches have
> been floating around for too long time to wait for another release
> cycle.  If there are problems, we can work on addressing them in
> follow up patches.

That's not how merge windows work.  The patches are merged when they are considered complete not when they are first posted.  The other patches I've applied are fixes for issues, not new functionality.  The new functionality is going into my 'next' branch.

- k

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