On Mon, Feb 29, 2016 at 10:06:05PM +0000, Eric Wheeler wrote:

On Mon, 29 Feb 2016, Greg KH wrote:

quoted

On Mon, Feb 29, 2016 at 08:06:58PM +0000, Eric Wheeler wrote:

quoted

On Sat, 27 Feb 2016, Greg KH wrote:

quoted

On Fri, Feb 26, 2016 at 05:34:19PM -0800, Eric Wheeler wrote:

quoted

To whom it may concern:

Please flag commit cbf76b702 for inclusion into stable branches.  It 
applies cleanly in 4.1 (and likely 3.18).  We have been testing it for a 
while.

git diff --stat cbf76b702~1..cbf76b702
 drivers/md/bcache/closure.c | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

Thank you!

$ git show cbf76b702
fatal: ambiguous argument 'cbf76b702': unknown revision or path not in the working tree.

You are going to have to be a bit more specific...

This one:


commit cbf76b702e85802683c166ad9067874bc3e1e843
Author: Petr Mladek [off-list ref]
Date:   Mon Oct 5 14:39:52 2015 +0200

There is no such commit in Linus's tree.

Hmm, not sure where that commit hash came from then.  Here it is properly:
  	8d090f47315507c3064ca4eefa9a1da52390b52e 

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8d090f47315507c3064ca4eefa9a1da52390b52e

That's better.

But this is just a debugging patch, for a debugfs file, how does it
follow the rules outlined in Documentation/stable_kernel_rules.txt for
what is acceptable for a stable kernel release?

greg k-h