[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <53A0EE13.9070208@oracle.com>
Date: Wed, 18 Jun 2014 09:40:35 +0800
From: Jeff Liu <jeff.liu@...cle.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: James Bottomley <James.Bottomley@...senPartnership.com>,
Christoph Lameter <cl@...two.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Pekka Enberg <penberg@...nel.org>,
Matt Mackall <mpm@...enic.com>, benh@...nel.crashing.org,
paulus@...ba.org, schwidefsky@...ibm.com,
heiko.carstens@...ibm.com, herbert@...dor.apana.org.au,
davem@...emloft.net, stefanr@...6.in-berlin.de, joro@...tes.org,
jejb@...isc-linux.org, deller@....de, bhelgaas@...gle.com,
clm@...com, Josef Bacik <jbacik@...com>, swhiteho@...hat.com,
bharrosh@...asas.com, bhalevy@...marydata.com, ccaulfie@...hat.com,
teigland@...hat.com, "Theodore Ts'o" <tytso@....edu>,
adilger.kernel@...ger.ca, jaegeuk@...nel.org,
cm224.lee@...sung.com, Mark Fasheh <mfasheh@...e.com>,
Joel Becker <jlbec@...lplan.org>, casey@...aufler-ca.com,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 01/24] kobject: return actual error on kset_create_and_add
On 06/17/2014 23:50 PM, Greg KH wrote:
> On Tue, Jun 17, 2014 at 10:56:04PM +0800, Jeff Liu wrote:
>>
>> On 06/17/2014 22:42 PM, James Bottomley wrote:
>>> On Tue, 2014-06-17 at 22:25 +0800, Jeff Liu wrote:
>>>> From: Jie Liu <jeff.liu@...cle.com>
>>>>
>>>> It's better to return the actual error rather than NULL because
>>>> kset_register() can failed due to other reasons.
>>>>
<snip>
>>>>
>>>
>>> This patch series isn't bisectable. When changing an error signal from
>>> NULL to non-NULL, you have to do it as one patch, otherwise if a
>>> bisection lands in here we'll get error returns from all our kobject
>>> kset code and the kernel won't boot.
>>
>> Thanks for pointing this out.
>>
>>> It's fine if you're sending it out as 24 patches for review, but it has
>>> to be applied as a single one.
>>
>> Ok, I'll post the v2 patch as a single one once this series has been reviewed.
>
> Also, now that you sent a bunch of different patches out, some
> maintainers will not realize that this first one has to be applied (i.e.
> you gave them no sense that there was a dependancy.)
>
> You will have to watch very carefully to ensure that those patches do
> not now get accepted, as they will break the existing code.
Ok, and I'll inform every other maintainers do not apply their patch individually.
Cheers,
-Jeff
--
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