From: Christoph Hellwig <hch@infradead.org>
To: aelder@sgi.com, xfs@oss.sgi.com, akpm@linux-foundation.org,
sfr@canb.auug.org.au
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/5] XFS fixes for 2.6.32
Date: Tue, 06 Oct 2009 16:29:25 -0400 [thread overview]
Message-ID: <20091006202925.459164320@bombadil.infradead.org> (raw)
This is my queue of reviewed patches from before or the very early merge indow
that I still haven't managed to get maintainer responses for. Thery're
all pretty crictical sync / metadata fixes that should not miss 2.6.32.
Andrew, Stephen can you carry them in -mm/linux-next at least until the
Alex reappears?
There's also a tarball of the quilt series at:
http://verein.lst.de/~hch/xfs/patches.xfs.tgz
I have another series of potentioal deadlock fixes that still needs a positive
review still but could also enjoy some more testing in -mm/linux-next which
I'll send out later today or tomorrow.
next reply other threads:[~2009-10-06 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 20:29 Christoph Hellwig [this message]
2009-10-06 20:29 ` [PATCH 1/5] xfs: implement ->dirty_inode to fix timestamp handling Christoph Hellwig
2009-10-06 20:29 ` [PATCH 2/5] [PATCH 5/5] xfs: fix xfs_quiesce_data Christoph Hellwig
2009-10-06 20:29 ` [PATCH 3/5] [PATCH 2/5] xfs: cleanup ->sync_fs Christoph Hellwig
2009-10-06 20:29 ` [PATCH 4/5] xfs: mark inodes dirty before issuing I/O Christoph Hellwig
2009-10-06 20:29 ` [PATCH 5/5] xfs: make sure xfs_sync_fsdata covers the log Christoph Hellwig
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=20091006202925.459164320@bombadil.infradead.org \
--to=hch@infradead.org \
--cc=aelder@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xfs@oss.sgi.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 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).