Re: [RFC 1/8] locking: Move mutex into kernel/locking/

[Ingo Molnar]

* Ingo Molnar <mingo@xxxxxxxxxx> wrote:

> * Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:
> 
> > On Tue, Nov 05, 2013 at 12:26:38PM -0800, Michel Lespinasse wrote:
> > > On Tue, Nov 5, 2013 at 4:10 AM, Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:
> > > > Index: linux-2.6/kernel/Makefile
> > > > ===================================================================
> > > > --- linux-2.6.orig/kernel/Makefile
> > > > +++ linux-2.6/kernel/Makefile
> > > > @@ -7,7 +7,7 @@ obj-y     = fork.o exec_domain.o panic.o
> > > >             sysctl.o sysctl_binary.o capability.o ptrace.o timer.o user.o \
> > > >             signal.o sys.o kmod.o workqueue.o pid.o task_work.o \
> > > >             extable.o params.o posix-timers.o \
> > > > -           kthread.o sys_ni.o posix-cpu-timers.o mutex.o \
> > > > +           kthread.o sys_ni.o posix-cpu-timers.o \
> > > >             hrtimer.o rwsem.o nsproxy.o semaphore.o \
> > > >             notifier.o ksysfs.o cred.o reboot.o \
> > > >             async.o range.o groups.o lglock.o smpboot.o
> > > 
> > > 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.
> 
> Please do it against the locking tree (tip:core/locking), it has pending 
> changes plus v3.12 as well.

Note, I pushed out the movement patches to tip:core/locking, anyone 
interested in testing it can pick them up from there.

Thanks,

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