From: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
To: Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL] Bcache fixes for 3.11
Date: Tue, 16 Jul 2013 21:11:05 -0600 [thread overview]
Message-ID: <20130717031105.GW22392@kernel.dk> (raw)
In-Reply-To: <20130716211221.GD27000@kmo-pixel>
On Tue, Jul 16 2013, Kent Overstreet wrote:
> Hey Jens - I've been busy torture testing and chasing bugs, here's the
> fruits of my labors. These are all fairly small fixes, some of them
> quite important:
>
> The following changes since commit 8e51e414a3c6d92ef2cc41720c67342a8e2c0bf7:
>
> bcache: Use standard utility code (2013-07-01 14:43:53 -0700)
>
> are available in the git repository at:
>
> git://evilpiepirate.org/~kent/linux-bcache.git bcache-for-3.11
>
> for you to fetch changes up to 79826c35eb99cd3c0873b8396f45fa26c87fb0b0:
>
> bcache: Allocation kthread fixes (2013-07-12 00:22:49 -0700)
Thanks Kent, pulled in for 3.11. Due to my recent move, the 3.11 drivers
pull is delayed a bit, will go out shortly.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
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.11
Date: Tue, 16 Jul 2013 21:11:05 -0600 [thread overview]
Message-ID: <20130717031105.GW22392@kernel.dk> (raw)
In-Reply-To: <20130716211221.GD27000@kmo-pixel>
On Tue, Jul 16 2013, Kent Overstreet wrote:
> Hey Jens - I've been busy torture testing and chasing bugs, here's the
> fruits of my labors. These are all fairly small fixes, some of them
> quite important:
>
> The following changes since commit 8e51e414a3c6d92ef2cc41720c67342a8e2c0bf7:
>
> bcache: Use standard utility code (2013-07-01 14:43:53 -0700)
>
> are available in the git repository at:
>
> git://evilpiepirate.org/~kent/linux-bcache.git bcache-for-3.11
>
> for you to fetch changes up to 79826c35eb99cd3c0873b8396f45fa26c87fb0b0:
>
> bcache: Allocation kthread fixes (2013-07-12 00:22:49 -0700)
Thanks Kent, pulled in for 3.11. Due to my recent move, the 3.11 drivers
pull is delayed a bit, will go out shortly.
--
Jens Axboe
next prev parent reply other threads:[~2013-07-17 3:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 21:12 [GIT PULL] Bcache fixes for 3.11 Kent Overstreet
2013-07-16 21:12 ` Kent Overstreet
2013-07-17 3:11 ` Jens Axboe [this message]
2013-07-17 3:11 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2013-08-14 22:59 [GIT PULL] bcache " Kent Overstreet
2013-08-14 22:59 ` Kent Overstreet
2013-08-15 6:43 ` Stefan Priebe - Profihost AG
2013-08-15 6:43 ` Stefan Priebe - Profihost AG
2013-08-15 7:07 ` Kent Overstreet
[not found] ` <520C788A.1060208-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-08-16 10:11 ` Stefan Priebe - Profihost AG
2013-08-16 10:11 ` Stefan Priebe - Profihost AG
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=20130717031105.GW22392@kernel.dk \
--to=axboe-tswwg44o7x1aa/9udqfwiw@public.gmane.org \
--cc=kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.