[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwHk20Go1bZwwNpNXaLsQEV2DC4tsbfOp21ufz7VGq_VQ@mail.gmail.com>
Date: Tue, 3 Sep 2013 08:38:40 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Sedat Dilek <sedat.dilek@...il.com>
Cc: Ingo Molnar <mingo@...nel.org>, Waiman Long <waiman.long@...com>,
Al Viro <viro@...iv.linux.org.uk>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Jeff Layton <jlayton@...hat.com>,
Miklos Szeredi <mszeredi@...e.cz>,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Andi Kleen <andi@...stfloor.org>,
"Chandramouleeswaran, Aswin" <aswin@...com>,
"Norton, Scott J" <scott.norton@...com>
Subject: Re: [PATCH v7 1/4] spinlock: A new lockref structure for lockless
update of refcount
On Tue, Sep 3, 2013 at 12:24 AM, Sedat Dilek <sedat.dilek@...il.com> wrote:
>
> Can someone summarize this thread (70+ postings)?
> Which patches are needed? And fixing what?
> ( Can people provide separate patches with a proper changelog? )
> Improvements?
The core lockref part is now merged and available in my git tree (and
yes, as individual patches with proper logs).
Al's patch to avoid the lg_lock is still pending, I'm assuming I'll
get it through his VFS tree.
Linus
--
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