[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1205151338120.583@chino.kir.corp.google.com>
Date: Tue, 15 May 2012 13:39:57 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: "Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
cc: a.p.zijlstra@...llo.nl, mingo@...nel.org, pjt@...gle.com,
paul@...lmenage.org, akpm@...ux-foundation.org, rjw@...k.pl,
nacc@...ibm.com, paulmck@...ux.vnet.ibm.com, tglx@...utronix.de,
seto.hidetoshi@...fujitsu.com, tj@...nel.org, mschmidt@...hat.com,
berrange@...hat.com, nikunj@...ux.vnet.ibm.com,
vatsa@...ux.vnet.ibm.com, liuj97@...il.com,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH v3 4/5] cpusets: Add provisions for distinguishing CPU
Hotplug in suspend/resume path
On Wed, 16 May 2012, Srivatsa S. Bhat wrote:
> > Your change, once merged, will not carry patch 0/5 here, so it would be
> > helpful to understand why we need to distinguish between the two as a
> > stand-alone patch in your changelog.
> >
>
>
> Sorry, I didn't quite get your point. Do you just want me to update this
> changelog or do you still want me to squash this patch with patch 5?
>
I think it should either be folded into patch 5 or the changelog updated
to reflect why we need to distinguish between hotplug and suspend; the
text from patch 0 will not be carried along to git so as a stand-alone
commit in Linus' tree, it's confusing why this is being done.
--
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/
Powered by blists - more mailing lists