From: Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
To: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL] bcache changes for 3.13
Date: Mon, 4 Nov 2013 12:16:11 -0800 [thread overview]
Message-ID: <20131104201611.GB27733@kmo> (raw)
In-Reply-To: <5277FFA1.6060001-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
On Mon, Nov 04, 2013 at 01:12:17PM -0700, Jens Axboe wrote:
> On 11/04/2013 01:07 PM, Kent Overstreet wrote:
> > Hey Jens, sorry for being late with this - anyways, it's roughly the same set of
> > patches you had queued up before plus a few minor fixes, but it's been rebased
> > onto your for-3.13/core branch.
>
> Merge window is a little later this time, and since it was already in
> for the previous release, we can make it happen.
>
> But can you please base it on for-3.13/drivers however? That's where I'd
> like to pull in the driver bits, and if I pull this one, then things get
> even more tangled since for-3.13/core is holding the blk-mq changes too.
I'd like to do the merge with immutable biovecs myself though - there's some
tricky bits in there. How will that work?
WARNING: multiple messages have this Message-ID (diff)
From: Kent Overstreet <kmo@daterainc.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, linux-bcache@vger.kernel.org
Subject: Re: [GIT PULL] bcache changes for 3.13
Date: Mon, 4 Nov 2013 12:16:11 -0800 [thread overview]
Message-ID: <20131104201611.GB27733@kmo> (raw)
In-Reply-To: <5277FFA1.6060001@kernel.dk>
On Mon, Nov 04, 2013 at 01:12:17PM -0700, Jens Axboe wrote:
> On 11/04/2013 01:07 PM, Kent Overstreet wrote:
> > Hey Jens, sorry for being late with this - anyways, it's roughly the same set of
> > patches you had queued up before plus a few minor fixes, but it's been rebased
> > onto your for-3.13/core branch.
>
> Merge window is a little later this time, and since it was already in
> for the previous release, we can make it happen.
>
> But can you please base it on for-3.13/drivers however? That's where I'd
> like to pull in the driver bits, and if I pull this one, then things get
> even more tangled since for-3.13/core is holding the blk-mq changes too.
I'd like to do the merge with immutable biovecs myself though - there's some
tricky bits in there. How will that work?
next prev parent reply other threads:[~2013-11-04 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 20:07 [GIT PULL] bcache changes for 3.13 Kent Overstreet
2013-11-04 20:07 ` Kent Overstreet
2013-11-04 20:12 ` Jens Axboe
2013-11-04 20:12 ` Jens Axboe
[not found] ` <5277FFA1.6060001-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2013-11-04 20:16 ` Kent Overstreet [this message]
2013-11-04 20:16 ` Kent Overstreet
2013-11-04 20:16 ` Jens Axboe
2013-11-04 20:16 ` Jens Axboe
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=20131104201611.GB27733@kmo \
--to=kmo-pezghdh756f8ursed/g0lq@public.gmane.org \
--cc=axboe-tSWWG44O7X1aa/9Udqfwiw@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.