From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Subject: Re: [PATCH 0/2] 2.6.29 queue
Date: Thu, 12 Feb 2009 14:19:50 -0500 [thread overview]
Message-ID: <20090212191950.GA27823@infradead.org> (raw)
In-Reply-To: <20090210194422.767988000@bombadil.infradead.org>
On Tue, Feb 10, 2009 at 02:44:22PM -0500, Christoph Hellwig wrote:
> Two more updates for 2.6.29, one to fix a possible oops when we're out
> of memory in xfs_log_mount and one to reject swapext on swapfiles.
Thanks for the reviews!
The patches are now available to pull from:
git://git.kernel.org/pub/scm/fs/xfs/xfs.git
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-02-12 19:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 19:44 [PATCH 0/2] 2.6.29 queue Christoph Hellwig
2009-02-10 19:44 ` [PATCH 1/2] xfs: fix error handling in xfs_log_mount Christoph Hellwig
2009-02-10 19:56 ` Felix Blyakher
2009-02-10 19:57 ` Christoph Hellwig
2009-02-10 20:09 ` Felix Blyakher
2009-02-10 23:24 ` Lachlan McIlroy
2009-02-11 22:39 ` Christoph Hellwig
2009-02-10 19:44 ` [PATCH 2/2] xfs: reject swapext ioctl on swapfiles Christoph Hellwig
2009-02-10 20:00 ` Felix Blyakher
2009-02-12 19:19 ` Christoph Hellwig [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=20090212191950.GA27823@infradead.org \
--to=hch@infradead.org \
--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