public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Ajeet Yadav <ajeet.yadav.77@gmail.com>, xfs@oss.sgi.com
Subject: Re: "xfs: fix error handling for synchronous writes" revisited
Date: Wed, 10 Aug 2011 08:20:11 -0500	[thread overview]
Message-ID: <1312982411.2865.1.camel@doink> (raw)
In-Reply-To: <20110810100916.GA27094@infradead.org>

On Wed, 2011-08-10 at 06:09 -0400, Christoph Hellwig wrote:
> Looks good.
> 
> Alex, any chance to pick this one up for 3.1?

Yes.  I'm working through patches today.  I'll make
sure this gets included in what I'm working with and
I should have it to Linus by Friday.

					-Alex

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2011-08-10 13:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 10:51 "xfs: fix error handling for synchronous writes" revisited Ajeet Yadav
2011-07-28 14:50 ` Christoph Hellwig
2011-07-29  7:42   ` Ajeet Yadav
2011-08-10 10:09     ` Christoph Hellwig
2011-08-10 13:20       ` Alex Elder [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=1312982411.2865.1.camel@doink \
    --to=aelder@sgi.com \
    --cc=ajeet.yadav.77@gmail.com \
    --cc=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