Re: [PATCH 01/12] Use mutex instead of semaphore in driver core



From your previous mail
You need to actually boot the kernel to get effective reports from
lockdep, it'll build just fine.

I will post the config file and dmesg with lockdep messages after a while.

On Dec 29, 2007 9:57 AM, Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:

On Sat, 2007-12-29 at 09:52 +0800, Dave Young wrote:

Hm, actually it's not so hard, but If I resend the 12 patches seems
like spam to lkml :-).

Of cource, if you all don't mind and it is really needed, I will do that.

As it stands now I'm quite convinced these patches will make lockdep
scream bloody murder, so these patches would need quite some more work
before they're usable.


Also, I don't think your series is bisectable, ie. 1/12 changes
device::sem -> device::mutex, and 12/12 changes a user of it.

Sorry, I don't use git tools now. Could you tell me how to fix it?
thanks in advance.

Just ensure that the kernel builds after each applied patch. If you're
using quilt, something like:

while (quilt push && make)
should finish the whole series.

Thanks a lot.

Regards
dave



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages