[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140312042616.GX13647@dastard>
Date: Wed, 12 Mar 2014 15:26:16 +1100
From: Dave Chinner <david@...morbit.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Peter Zijlstra <peterz@...radead.org>,
Waiman Long <waiman.long@...com>, arnd@...db.de,
linux-arch@...r.kernel.org, x86@...nel.org,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
walken@...gle.com, andi@...stfloor.org, riel@...hat.com,
paulmck@...ux.vnet.ibm.com, torvalds@...ux-foundation.org,
oleg@...hat.com
Subject: Re: [RFC][PATCH 0/7] locking: qspinlock
On Tue, Mar 11, 2014 at 11:11:59PM -0400, Steven Rostedt wrote:
> On Wed, 12 Mar 2014 13:31:53 +1100
> Dave Chinner <david@...morbit.com> wrote:
>
>
> > So either this patchset doesn't work right now, or there's something
> > else broken in the tip/master tree...
>
> I've found a few things broken with the tip master tree. Anyway, I'm
> not sure the patches are even there. The last I saw, the patches are
> still in RFC stage. Might want to take a known working kernel and apply
> the patches manually.
I did apply them manually - but the patchset is based on the
tip/master, plus some patches from a previous patch set that aren't
in tip/locking to be able to apply this patchset cleanly in the
first place. So there's no "start froma known working kernel" case
that applies here :/
Cheers,
Dave.
--
Dave Chinner
david@...morbit.com
--
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