[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0805071509270.3024@woody.linux-foundation.org>
Date: Wed, 7 May 2008 15:11:10 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andrea Arcangeli <andrea@...ranet.com>
cc: Andrew Morton <akpm@...ux-foundation.org>, clameter@....com,
steiner@....com, holt@....com, npiggin@...e.de,
a.p.zijlstra@...llo.nl, kvm-devel@...ts.sourceforge.net,
kanojsarcar@...oo.com, rdreier@...co.com,
swise@...ngridcomputing.com, linux-kernel@...r.kernel.org,
avi@...ranet.com, linux-mm@...ck.org,
general@...ts.openfabrics.org, hugh@...itas.com,
rusty@...tcorp.com.au, aliguori@...ibm.com, chrisw@...hat.com,
marcelo@...ck.org, dada1@...mosbay.com, paulmck@...ibm.com
Subject: Re: [PATCH 01 of 11] mmu-notifier-core
On Wed, 7 May 2008, Andrea Arcangeli wrote:
> > As far as I can tell, authorship has been destroyed by at least two of the
> > patches (ie Christoph seems to be the author, but Andrea seems to have
> > dropped that fact).
>
> I can't follow this, please be more specific.
The patches were sent to lkml without *any* indication that you weren't
actually the author.
So if Andrew had merged them, they would have been merged as yours.
> > That "locking" code is also too ugly to live, at least without some
> > serious arguments for why it has to be done that way. Sorting the locks?
> > In a vmalloc'ed area? And calling this something innocuous like
> > "mm_lock()"? Hell no.
>
> That's only invoked in mmu_notifier_register, mm_lock is explicitly
> documented as heavyweight function.
Is that an excuse for UTTER AND TOTAL CRAP?
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