[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080520193314.061f0c24@core>
Date: Tue, 20 May 2008 19:33:14 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Arjan van de Ven <arjan@...radead.org>
Cc: Andi Kleen <andi@...stfloor.org>, corbet@....net,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [2/11] Add unlocked_fasync
On Tue, 20 May 2008 08:58:30 -0700
Arjan van de Ven <arjan@...radead.org> wrote:
> On Tue, 20 May 2008 17:28:43 +0200 (CEST)
> Andi Kleen <andi@...stfloor.org> wrote:
>
> >
> > Add a new fops entry point to allow fasync without BKL.
>
> I (again) really don't like having another entry point for this...
> it'll stay around forever rather than doing this as one step and
> move on.
Agreed entirely - all our unlocked_foo methods we got stuck with, all our
push down everyone cases we got most cases promptly fixed and the other
lock/unlocks show up clearly in grep and help embarass the
maintainer/author 8)
--
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