Re: [PATCH 5.1 00/40] 5.1.7-stable review
From: Greg Kroah-Hartman
Date: Tue Jun 04 2019 - 01:53:39 EST
On Mon, Jun 03, 2019 at 11:28:23AM -0700, Kevin Hilman wrote:
> "kernelci.org bot" <bot@xxxxxxxxxxxx> writes:
> > stable-rc/linux-5.1.y boot: 132 boots: 1 failed, 131 passed (v5.1.6-41-ge674455b9242)
> > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.1.y/kernel/v5.1.6-41-ge674455b9242/
> > Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.1.y/kernel/v5.1.6-41-ge674455b9242/
> > Tree: stable-rc
> > Branch: linux-5.1.y
> > Git Describe: v5.1.6-41-ge674455b9242
> > Git Commit: e674455b924207b06e6527d961a4b617cf13e7a9
> > Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > Tested: 73 unique boards, 23 SoC families, 14 builds out of 209
> > Boot Failure Detected:
> > arm:
> > multi_v7_defconfig:
> > gcc-8:
> > bcm4708-smartrg-sr400ac: 1 failed lab
> FYI, this one has been fixed and marked with Fixes tag, but it
> appears the patch hasn't yet landed in mainline.
A Fixes: tag will not guarantee it will make it into a stable release.
It might, a month or so later, if we get bored. You should always use a
Cc: stable@ tag instead, as that is the documented way to ensure that
the patch makes it into a stable release.
Once this hits Linus's tree, send me the SHA1 and I will be glad to
queue it up.