[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANN689FKEy3cc9EGOViY-kev1hJ-8DR1RB_4hya0jkJfahSQug@mail.gmail.com>
Date: Tue, 5 Nov 2013 13:24:44 -0800
From: Michel Lespinasse <walken@...gle.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
paulmck@...ux.vnet.ibm.com, oleg@...hat.com, dhowells@...hat.com,
willy@...ux.intel.com, tglx@...utronix.de, rostedt@...dmis.org,
airlied@...il.com, maarten.lankhorst@...onical.com,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>
Subject: Re: [RFC 1/8] locking: Move mutex into kernel/locking/
On Tue, Nov 5, 2013 at 1:20 PM, Peter Zijlstra <peterz@...radead.org> wrote:
>> This is probably a stupid question, but I haven't been able to find
>> one kernel version that this applies cleanly over ???
>
> Oh my bad, it appears I made it against a working tree, not an actual
> published tree. That said, I don't think the rejects should be super
> hard to fix.
>
> If people don't object to the idea I'll respin against something
> published and testable.
Yes please.
The reason I want to apply this is because code moves cause noisy
patches, and the easiest way I know to fully figure them out is to
diff them against a private tree where I have moved the same files
(yeah, there really ought to be a better way, ....)
--
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.
--
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