From: Jens Axboe <axboe@kernel.dk>
To: Kent Overstreet <kmo@daterainc.com>
Cc: linux-kernel@vger.kernel.org, linux-bcache@vger.kernel.org
Subject: Re: [GIT PULL] bcache fixes for 3.13
Date: Tue, 17 Dec 2013 12:53:24 -0700 [thread overview]
Message-ID: <20131217195324.GD24924@kernel.dk> (raw)
In-Reply-To: <20131216222409.GD4054@kmo>
On Mon, Dec 16 2013, Kent Overstreet wrote:
> Jens - small pile of bcache fixes. I've been slacking on the writeback fixes but
> those definitely need to get into 3.13:
>
> The following changes since commit c86949486d41d9e7d7681fc72923555114fd702f:
>
> bcache: defensively handle format strings (2013-11-10 21:56:43 -0800)
>
> are available in the git repository at:
>
> git://evilpiepirate.org/~kent/linux-bcache.git bcache-for-3.13
>
> for you to fetch changes up to 16749c23c00c686ed168471963e3ddb0f3fcd855:
>
> bcache: New writeback PD controller (2013-12-16 14:22:59 -0800)
Thanks Kent, pulled.
--
Jens Axboe
prev parent reply other threads:[~2013-12-17 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 22:24 [GIT PULL] bcache fixes for 3.13 Kent Overstreet
2013-12-17 19:53 ` 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=20131217195324.GD24924@kernel.dk \
--to=axboe@kernel.dk \
--cc=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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).