From: Matt Mackall <mpm@selenic.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
Davide Libenzi <davidel@xmailserver.org>,
David Miller <davem@davemloft.net>,
Christoph Hellwig <hch@lst.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH/RFC] Fasync BKL removal
Date: Sat, 07 Feb 2009 14:28:26 -0600 [thread overview]
Message-ID: <1234038506.3243.265.camel@calx> (raw)
In-Reply-To: <1234037217-16124-1-git-send-email-corbet@lwn.net>
On Sat, 2009-02-07 at 13:06 -0700, Jonathan Corbet wrote:
> With any luck at all, this is my final attempt at removing the BKL from the
> fasync() path and providing proper protection for struct file->f_flags.
> This week's episode includes these patches:
This all looks very pretty to me.
Acked-by: Matt Mackall <mpm@selenic.com>
--
http://selenic.com : development and support for Mercurial and Linux
prev parent reply other threads:[~2009-02-07 20:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 20:06 [PATCH/RFC] Fasync BKL removal Jonathan Corbet
2009-02-07 20:06 ` [PATCH 1/4] Rename struct file->f_ep_lock Jonathan Corbet
2009-02-08 8:56 ` Christoph Hellwig
2009-02-08 19:51 ` Davide Libenzi
2009-02-07 20:06 ` [PATCH 2/4] Use f_lock to protect f_flags Jonathan Corbet
2009-02-08 9:02 ` Christoph Hellwig
2009-02-07 20:06 ` [PATCH 3/4] Move FASYNC bit handling to f_op->fasync() Jonathan Corbet
2009-02-08 9:05 ` Christoph Hellwig
2009-02-10 2:41 ` Jonathan Corbet
2009-02-07 20:06 ` [PATCH 4/4] Rationalize fasync return values Jonathan Corbet
2009-02-07 20:28 ` Matt Mackall [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1234038506.3243.265.camel@calx \
--to=mpm@selenic.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=davidel@xmailserver.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.