From: Jens Axboe <axboe@kernel.dk>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: linux-bcache@vger.kernel.org,
Kent Overstreet <kent.overstreet@gmail.com>,
Kai Krakow <kai@kaishome.de>, Wido den Hollander <wido@widodh.nl>
Subject: Re: [PULL] bcache: multiple updates
Date: Thu, 27 Oct 2016 19:12:33 -0600 [thread overview]
Message-ID: <5160da7c-e38e-1527-2b09-2ca240df57c3@kernel.dk> (raw)
In-Reply-To: <alpine.LRH.2.11.1610262037160.24191@mail.ewheeler.net>
On 10/27/2016 05:27 PM, Eric Wheeler wrote:
> Hi Jens,
>
> Please pull this v4.9-rc2 based series of bcache updates for v4.9-rc3:
> (You may disregard the previous -rc1-based request.)
>
> git pull https://bitbucket.org/ewheelerinc/linux.git v4.9-rc2-bcache-updates
>
> Thank you!
>
> --
> Eric Wheeler
>
> ]# git log --oneline v4.9-rc2..HEAD
> bd532a6 bcache: partition support: add 16 minors per bcacheN device
> 3312845 bcache: Make gc wakeup sane, remove set_task_state()
> 6bb7f1e bcache: update bio->bi_opf bypass/writeback REQ_ flag hints
> 3d58a09 bcache: documentation for ioprio cache hinting
> 2e8884b bcache: introduce per-process ioprio-based bypass/writeback hints
How many of these are applicable to 4.9-rc3? I took a quick look at
them, and some of them look like they should go into the 4.10 branch
instead. We're after the merge window, so only strict fixes. Cleanups
and no features, no go.
--
Jens Axboe
next prev parent reply other threads:[~2016-10-28 1:13 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 [this message]
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
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=5160da7c-e38e-1527-2b09-2ca240df57c3@kernel.dk \
--to=axboe@kernel.dk \
--cc=bcache@lists.ewheeler.net \
--cc=kai@kaishome.de \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox