From: Greg KH <gregkh@linuxfoundation.org>
To: Eric Wheeler <stable@lists.ewheeler.net>
Cc: <stable@vger.kernel.org>
Subject: Re: [commit cbf76b702] bcache: Really show state of work pending bit
Date: Mon, 29 Feb 2016 21:29:08 +0000 [thread overview]
Message-ID: <20160229212907.GA437@kroah.com> (raw)
In-Reply-To: <alpine.LRH.2.11.1602292003090.3635@mail.ewheeler.net>
On Mon, Feb 29, 2016 at 08:06:58PM +0000, Eric Wheeler wrote:
> On Sat, 27 Feb 2016, Greg KH wrote:
> > On Fri, Feb 26, 2016 at 05:34:19PM -0800, Eric Wheeler wrote:
> > > 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 <pmladek@suse.com>
> Date: Mon Oct 5 14:39:52 2015 +0200
There is no such commit in Linus's tree.
confused,
greg k-h
next prev parent reply other threads:[~2016-02-29 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 1:34 [commit cbf76b702] bcache: Really show state of work pending bit Eric Wheeler
2016-02-27 6:17 ` Greg KH
2016-02-29 20:06 ` Eric Wheeler
2016-02-29 21:29 ` Greg KH [this message]
2016-02-29 22:06 ` Eric Wheeler
2016-02-29 22:31 ` Greg KH
2016-02-29 23:02 ` 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=20160229212907.GA437@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=stable@lists.ewheeler.net \
--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.