From: Jens Axboe <axboe@kernel.dk>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
linux-bcache@vger.kernel.org, dave@stgolabs.net,
linux-kernel@vger.kernel.org, Kai Krakow <kai@kaishome.de>,
Wido den Hollander <wido@widodh.nl>,
Emmanuel Florac <eflorac@intellique.com>,
Hans van den Bogert <hansbogert@gmail.com>,
"Jens-U. Mozdzen" <jmozdzen@nde.ag>
Subject: Re: [PULL] bcache: based on for-4.10/block, multiple updates
Date: Tue, 31 Jan 2017 11:27:59 -0800 [thread overview]
Message-ID: <15228b09-e185-7587-c905-700ca878e80f@kernel.dk> (raw)
In-Reply-To: <alpine.LRH.2.11.1701311103140.28608@mail.ewheeler.net>
On 01/31/2017 11:14 AM, Eric Wheeler wrote:
> On Wed, 14 Dec 2016, Jens Axboe wrote:
>> On 12/14/2016 06:50 PM, Eric Wheeler wrote:
>>> Hi Jens,
>>>
>>> I know you're busy, so when you get a moment:
>>>
>>> I've not yet seen your ack/nack on this yet and I want to make sure it
>>> gets in before the merge window closes for v4.10. I rebased it on
>>> for-4.10/block as you asked so its tested and ready to go as of 12/6
>>> unless you see something that I've missed.
>>
>> Pulled for 4.10, sorry about the delay.
>
> Hi Jens,
>
> Looking at 4.10-rc6, I see these two commits were merged:
>
>> bcache: partition support: add 16 minors per bcacheN device
>> bcache: Make gc wakeup sane, remove set_task_state()
>
> but these were in the same 'for-4.10-block-bcache-updates' and don't
> appear to have been applied:
>
>> bcache: introduce per-process ioprio-based bypass/writeback hints
>> bcache: documentation for ioprio cache hinting
>> bcache: update bio->bi_opf bypass/writeback REQ_ flag hints
>
> Did I miss an email that caused their exclusion?
>
> Did these get bumped to 4.11 for some reason?
I thought I sent out that reply, maybe I didn't. I dropped the
last three for two reasons:
1) They happened after the merge window, and it's really a feature
addon that should have gone in earlier
2) There seemed to be confusion and discussion around the interface
that needed to be resolved first.
Hope that explains it.
--
Jens Axboe
next prev parent reply other threads:[~2017-01-31 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 23:27 [PULL] bcache: multiple updates Eric Wheeler
2016-10-28 1:12 ` Jens Axboe
2016-10-30 1:32 ` Eric Wheeler
2016-10-30 3:44 ` Davidlohr Bueso
2016-10-30 14:00 ` Kent Overstreet
2016-10-30 15:01 ` Jens Axboe
2016-11-01 2:35 ` Eric Wheeler
2016-12-06 19:47 ` [PULL] bcache: based on for-4.10/block, " Eric Wheeler
2016-12-15 1:50 ` Eric Wheeler
2016-12-15 4:47 ` Jens Axboe
2017-01-31 19:14 ` Eric Wheeler
2017-01-31 19:27 ` Jens Axboe [this message]
2017-01-31 23:17 ` Eric Wheeler
2017-02-28 2:00 ` Eric Wheeler
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=15228b09-e185-7587-c905-700ca878e80f@kernel.dk \
--to=axboe@kernel.dk \
--cc=bcache@lists.ewheeler.net \
--cc=dave@stgolabs.net \
--cc=eflorac@intellique.com \
--cc=hansbogert@gmail.com \
--cc=jmozdzen@nde.ag \
--cc=kai@kaishome.de \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wido@widodh.nl \
/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.