From: "Jörn Engel" <joern@logfs.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@osdl.org>,
David Woodhouse <dwmw2@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: Re: LogFS merge
Date: Fri, 2 May 2008 22:33:52 +0200 [thread overview]
Message-ID: <20080502203352.GC24080@logfs.org> (raw)
In-Reply-To: <20080502153114.GA7376@infradead.org>
On Fri, 2 May 2008 11:31:14 -0400, Christoph Hellwig wrote:
> On Fri, May 02, 2008 at 05:49:38PM +0300, Pekka Enberg wrote:
> > You probably want an ACK from the VFS maintainers before aiming at
> > mainline. But it surely makes sense to ask Andrew to pull it in -mm
> > now.
>
> Definitively wants a re-review with all the bits from last time fixed.
>
> How did the inode_lock abuse get fixed, btw? That one was rather
> lethal.
That wart is still itching. I thought I'd need a core patch to remove
it, but looking at it again, I might get away with a private spinlock.
Will get fixed.
Jörn
--
Happiness isn't having what you want, it's wanting what you have.
-- unknown
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-05-02 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080502133234.GA24080@logfs.org>
2008-05-02 14:49 ` LogFS merge Pekka Enberg
2008-05-02 15:31 ` Christoph Hellwig
2008-05-02 20:33 ` Jörn Engel [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=20080502203352.GC24080@logfs.org \
--to=joern@logfs.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dwmw2@infradead.org \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).