On Mon, Aug 12, 2019 at 01:04:24PM +0800, Coly Li wrote:
> On 2019/8/12 12:09 上午, Greg KH wrote:
> > On Sun, Aug 11, 2019 at 11:41:57PM +0800, Coly Li wrote:
> >> On 2019/8/11 11:01 下午, gregkh@xxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxx>.
> >>>
> >>> 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()")
>
> Hi Greg,
>
> >
> > But commit 89e0341af082 showed up in 5.3-rc1, not 5.2.
> >
> > So why is this needed in 5.2.y?
>
> Indeed I was not sure which version this patch was merged, so I ran,
> > git describe 89e0341af082
> v5.2-rc4-245-g89e0341af082
>
> It seems I use git in an incorrect way. After check man git-describe I
> see '--contains' should be added (to find a tag which after/contains the
> commit),
> > git describe --contains 89e0341af082
> v5.3-rc1~164^2~57
>
> Yes, the fixing bug is from v5.3-rc1. Please ignore the noise....
No problem, thanks for the confirmation.
greg k-h
