From: David Chinner <dgc@sgi.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Filesystems <linux-fsdevel@vger.kernel.org>,
Mark Fasheh <mark.fasheh@oracle.com>,
Steven Whitehouse <swhiteho@redhat.com>
Subject: Re: [ANNOUNCE] new new aops patchset
Date: Thu, 5 Apr 2007 10:10:18 +1000 [thread overview]
Message-ID: <20070405001018.GK32602149@melbourne.sgi.com> (raw)
In-Reply-To: <20070402120934.GA19626@wotan.suse.de>
On Mon, Apr 02, 2007 at 02:09:34PM +0200, Nick Piggin wrote:
> Updated aops patchset against 2.6.21-rc5.
>
> http://www.kernel.org/pub/linux/kernel/people/npiggin/patches/new-aops/
>
> Files/dirs are 2.6.21-rc5-new-aops*
>
> Contains numerous fixes from Mark and myself -- I'd say the core code is
> getting reasonably stable at this point.
......
> (compile only) patches for NFS, XFS, FUSE, eCryptfs. OK, they're untested,
Failed to compile in UDF and reiser for me, but no doubt you know
that already. Don't have time to look at why - I just disabled them
so I get some QA done on the XFS and core changes.
On a related note - what's the rules for a perform_write() implementation?
I noticed that wasn't documented with write_begin and write_end and
I don't see any other filesystem implementing it yet....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-04-05 0:10 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 12:09 [ANNOUNCE] new new aops patchset Nick Piggin
2007-04-02 20:18 ` Badari Pulavarty
2007-04-03 0:45 ` Nick Piggin
2007-04-02 20:44 ` Badari Pulavarty
2007-04-02 23:58 ` Nick Piggin
2007-04-03 15:59 ` Badari Pulavarty
2007-04-04 2:33 ` Nick Piggin
2007-04-02 21:44 ` Badari Pulavarty
2007-04-02 23:08 ` Badari Pulavarty
2007-04-02 23:14 ` Badari Pulavarty
2007-04-02 23:49 ` Nick Piggin
2007-04-03 15:57 ` Badari Pulavarty
2007-04-04 2:31 ` Nick Piggin
2007-04-02 23:31 ` Badari Pulavarty
2007-04-02 23:35 ` Nick Piggin
2007-04-02 23:56 ` Badari Pulavarty
2007-04-03 0:02 ` Nick Piggin
2007-04-03 0:00 ` Badari Pulavarty
2007-04-03 0:08 ` Nick Piggin
2007-04-03 9:31 ` Nick Piggin
2007-04-03 16:03 ` Badari Pulavarty
2007-04-04 2:37 ` Nick Piggin
2007-04-03 17:35 ` Badari Pulavarty
2007-04-04 3:05 ` Nick Piggin
2007-04-04 22:10 ` Mark Fasheh
2007-04-04 22:39 ` Badari Pulavarty
2007-04-04 22:51 ` Mark Fasheh
2007-04-04 23:02 ` Badari Pulavarty
2007-04-04 23:05 ` Badari Pulavarty
2007-04-04 23:17 ` Mark Fasheh
2007-04-04 23:32 ` Badari Pulavarty
2007-04-05 2:08 ` Nick Piggin
2007-04-05 15:21 ` Badari Pulavarty
2007-04-06 1:38 ` Nick Piggin
2007-04-05 2:09 ` Nick Piggin
2007-04-05 0:10 ` David Chinner [this message]
2007-04-05 2:13 ` Nick Piggin
2007-04-05 7:45 ` Christoph Hellwig
2007-04-05 7:58 ` Nick Piggin
2007-04-05 2:43 ` David Chinner
2007-04-05 3:00 ` Nick Piggin
2007-04-05 6:18 ` David Chinner
2007-04-05 6:40 ` Nick Piggin
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=20070405001018.GK32602149@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=npiggin@suse.de \
--cc=swhiteho@redhat.com \
/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.