All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, Kent Overstreet <kmo@daterainc.com>
Cc: Peter Kieser <peter@kieser.ca>,
	linux-kernel@vger.kernel.org, linux-bcache@vger.kernel.org,
	stable <stable@vger.kernel.org>
Subject: Re: [GIT PULL] bcache changes for 3.17
Date: Fri, 05 Sep 2014 16:44:13 +0200	[thread overview]
Message-ID: <5409CC3D.7040009@gmail.com> (raw)
In-Reply-To: <5409C5FC.6020406@kernel.dk>

On 09/05/2014 04:17 PM, Jens Axboe wrote:
> 
> We need to do something about this. From this latest pull, looks like
> all should go to stable:
> 
> 5b1016e62f74c53e0330403025954c8d95384c03
> 9aa61a992acceeec0d1de2cd99938421498659d5
> dbd810ab678d262d3772d29b65844d7b20dc47bc
> 8b326d3a2a76912dfed2f0ab937d59fae9512ca2
> e5112201c1285841f8b565ece5d6ae7e0d7947a2
> a664d0f05a2ec02c8f042db536d84d15d6e19e81
> c5aa4a3157b55bdca18dd2a9d9f43314470b6d32
> 9e5c353510b26500bd6b8309823ac9ef2837b761
> bcf090e0040e30f8409e6a535a01e6473afb096f
> 501d52a90cbe652b41336c206ff0e95799d5a9b5
> 8e0948080670f6330229718b15a6a1a011d441ce
> 60ae81eee86dd7a520db8c1e3d702b49fc0418b5
> 913dc33fb2720fb5f979011664294137ddd8b13b
> 6b708de64adb6dc8319e7aeac922b46904fbeeec
> 400ffaa2acd72274e2c7293a9724382383bebf3e
> d83353b319d47ef8cce82467da6a25c2d558253f
> bf0c55c986540483c34ca640f2eef4c3314388b1
> c9a78332b42cbdcdd386a95192a716b67d1711a4
> 2452cc89063a2a6890368f185c4b6d7d8802175b
> 25abade29616d42d60f9bd5e6a5ad07f7314e39e
> 5b25abade29616d42d60f9bd5e6a5ad07f7314e3
> 789d21dbd9d8889e62c79ec19585fcc97e42ef07
> 0781c8748cf1ea2b0dcd966571103909528c4efa
> 
> (from oldest to newest). And that's just from 3.16 to 3.17-rc3, going
> all the way back to 3.10 would be a lot of work. If there's anyone that
> cares about bcache on stable kernels (and actually use it), now would be
> a good time to pipe up.
> 

Then if it's too much work, it just confirmed what was asked previously:
bcache is still experimental so mark it such for stable kernels.

I wouldn't have used bcache in that case.

Thanks

  parent reply	other threads:[~2014-09-05 14:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05  4:33 [GIT PULL] bcache changes for 3.17 Kent Overstreet
2014-08-05 16:58 ` Jens Axboe
2014-08-10  7:54   ` Peter Kieser
2014-09-05  7:31     ` Francis Moreau
2014-09-05 14:17       ` Jens Axboe
2014-09-05 14:28         ` Vasiliy Tolstov
2014-09-05 14:30           ` Jens Axboe
2014-09-05 14:44         ` Francis Moreau [this message]
2014-09-05 21:46           ` Greg KH
2014-09-05 15:37         ` Eddie Chapman
2014-09-05 16:41           ` Peter Kieser
2014-09-05 17:03             ` Arne Wiebalck
2014-09-05 17:10               ` Jens Axboe
2014-09-05 18:33                 ` Kent Overstreet
2014-09-05 18:46                   ` Stefan Priebe
2015-02-05 13:40                 ` Francis Moreau
2014-09-06  0:33               ` Chuck Ebbert
2014-09-05 21:45       ` Greg KH
2014-09-05 22:21         ` Jens Axboe
2014-09-08 15:26           ` Greg KH
2014-09-05 23:17         ` Peter Kieser
2014-09-08 15:27           ` Greg KH
2014-09-06  9:23         ` Francis Moreau

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=5409CC3D.7040009@gmail.com \
    --to=francis.moro@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=kmo@daterainc.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@kieser.ca \
    --cc=stable@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 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.