linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Philipp Reisner <philipp.reisner@linbit.com>,
	"drbd-dev@linbit.com" <drbd-dev@linbit.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Julia Lawall <julia@diku.dk>, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: linux-next: manual merge of the drbd tree with Linus' tree
Date: Tue, 1 Jun 2010 10:36:13 +0200	[thread overview]
Message-ID: <20100601083613.GC3564@kernel.dk> (raw)
In-Reply-To: <20100601083244.GA2496@infradead.org>

On Tue, Jun 01 2010, Christoph Hellwig wrote:
> Talking about the block tree: can we please get the two writeback
> reverts in?  -rc1 is copletly unsuable under heavy I/O loads as it
> stands.

Yes, it'll go out today, it was supposed to land in -rc1 :/

-- 
Jens Axboe

      reply	other threads:[~2010-06-01  8:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01  4:13 linux-next: manual merge of the drbd tree with Linus' tree Stephen Rothwell
2010-06-01  8:18 ` Christoph Hellwig
     [not found]   ` <20100601081823.GA29991-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2010-06-01  8:22     ` Stephen Rothwell
2010-06-01  8:31       ` Jens Axboe
2010-06-01  8:42         ` Stephen Rothwell
2010-06-01  8:53           ` Jens Axboe
2010-06-01 10:35             ` Stephen Rothwell
2010-06-01 10:45       ` Jens Axboe
2010-06-01 10:49         ` Stephen Rothwell
2010-06-01 10:50           ` Jens Axboe
2010-06-01  8:22   ` Jens Axboe
     [not found]     ` <20100601082246.GA3564-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2010-06-01  8:32       ` Christoph Hellwig
2010-06-01  8:36         ` Jens Axboe [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=20100601083613.GC3564@kernel.dk \
    --to=jaxboe@fusionio.com \
    --cc=drbd-dev@linbit.com \
    --cc=hch@infradead.org \
    --cc=julia@diku.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=philipp.reisner@linbit.com \
    --cc=sfr@canb.auug.org.au \
    --cc=viro@zeniv.linux.org.uk \
    /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).