All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: writeback tree status
Date: Mon, 11 Jul 2011 03:55:53 -0700	[thread overview]
Message-ID: <20110711105553.GA6373@localhost> (raw)
In-Reply-To: <20110711104207.GA20317@infradead.org>

Hi Christoph,

On Mon, Jul 11, 2011 at 06:42:07PM +0800, Christoph Hellwig wrote:
> Hi Wu,
> 
> what is the state of the writeback updates for Linux 3.1?  There's
> still a lot of changes in your fs-writeback branch, but not in the
> next branch yet.  I know some are still under discussion, but it would
> be good to get everything destined for Linux 3.1 into linux-next ASAP
> so that it will get some testing.

Big sorry.. I just merged the fs-writeback patches into the branch for
linux-next. It seemed that I was a bit too nervous to push patches into
linux-next. I've been testing them locally, so far, so good. Hope the
linux-next push won't cause too much trouble for the wider testers.

Thanks,
Fengguang

WARNING: multiple messages have this Message-ID (diff)
From: Wu Fengguang <fengguang.wu@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: writeback tree status
Date: Mon, 11 Jul 2011 03:55:53 -0700	[thread overview]
Message-ID: <20110711105553.GA6373@localhost> (raw)
In-Reply-To: <20110711104207.GA20317@infradead.org>

Hi Christoph,

On Mon, Jul 11, 2011 at 06:42:07PM +0800, Christoph Hellwig wrote:
> Hi Wu,
> 
> what is the state of the writeback updates for Linux 3.1?  There's
> still a lot of changes in your fs-writeback branch, but not in the
> next branch yet.  I know some are still under discussion, but it would
> be good to get everything destined for Linux 3.1 into linux-next ASAP
> so that it will get some testing.

Big sorry.. I just merged the fs-writeback patches into the branch for
linux-next. It seemed that I was a bit too nervous to push patches into
linux-next. I've been testing them locally, so far, so good. Hope the
linux-next push won't cause too much trouble for the wider testers.

Thanks,
Fengguang

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-07-11 10:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 10:42 writeback tree status Christoph Hellwig
2011-07-11 10:42 ` Christoph Hellwig
2011-07-11 10:55 ` Wu Fengguang [this message]
2011-07-11 10:55   ` Wu Fengguang

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=20110711105553.GA6373@localhost \
    --to=fengguang.wu@intel.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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.