All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Coly Li <colyli@suse.de>
Cc: alexandru.ardelean@analog.com, axboe@kernel.dk, pflin@suse.com,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] bcache: Revert "bcache: use sysfs_match_string() instead of" failed to apply to 5.2-stable tree
Date: Sun, 11 Aug 2019 18:09:59 +0200	[thread overview]
Message-ID: <20190811160959.GA8117@kroah.com> (raw)
In-Reply-To: <81d2423d-74dd-50ba-4a33-05306a1b13dd@suse.de>

On Sun, Aug 11, 2019 at 11:41:57PM +0800, Coly Li wrote:
> On 2019/8/11 11:01 下午, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 5.2-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> > 
> > thanks,
> > 
> > greg k-h
> 
> Hi Greg,
> 
> I will post a rebased patch for the 5.2-stable tree.

Is it really needed?

I ask because in the patch it says:

> > This bug was introduced in Linux v5.2, so this fix only applies to
> > Linux v5.2 is enough for stable tree maintainer.
> > 
> > Fixes: 89e0341af082 ("bcache: use sysfs_match_string() instead of __sysfs_match_string()")

But commit 89e0341af082 showed up in 5.3-rc1, not 5.2.

So why is this needed in 5.2.y?

thanks,

greg k-h

  reply	other threads:[~2019-08-11 16:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-11 15:01 FAILED: patch "[PATCH] bcache: Revert "bcache: use sysfs_match_string() instead of" failed to apply to 5.2-stable tree gregkh
2019-08-11 15:41 ` Coly Li
2019-08-11 16:09   ` Greg KH [this message]
2019-08-12  5:04     ` Coly Li
2019-08-12  5:27       ` Greg KH

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=20190811160959.GA8117@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexandru.ardelean@analog.com \
    --cc=axboe@kernel.dk \
    --cc=colyli@suse.de \
    --cc=pflin@suse.com \
    --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.