Re: [PATCH 5.4 000/434] 5.4.7-stable review

Guenter Roeck
2019-12-31T05:19:30Z

On Mon, Dec 30, 2019 at 08:42:04PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Dec 30, 2019 at 12:08:49PM -0600, Dan Rue wrote:
> > On Mon, Dec 30, 2019 at 06:45:22PM +0100, Greg Kroah-Hartman wrote:
> > > On Mon, Dec 30, 2019 at 10:34:37AM -0600, Dan Rue wrote:
> > > > On Sun, Dec 29, 2019 at 06:20:53PM +0100, Greg Kroah-Hartman wrote:
> > > > > This is the start of the stable review cycle for the 5.4.7 release.
> > > > > There are 434 patches in this series, all will be posted as a response
> > > > > to this one. If anyone has any issues with these being applied, please
> > > > > let me know.
> > > >
> > > > Results from Linaro’s test farm.
> > > > No regressions on arm64, arm, x86_64, and i386.
> > >
> > > Thanks for testing all of these and letting me know.
> > >
> > > But didn't you add perf build testing to your builds? That should have
> > > broken things, so I am guessing not :(
> >
> > We do build (and run) perf, and it worked for us. Which patch was the
> > problem? I can go look at why our config didn't hit the offending
> > code/build path.
>
> See the thread from Guenter and from others on the perf patches
> themselves in this release for the details.
>

perf is a beast. It only builds everything if a large number of
support libraries is installed on the build system. If not, it
only builds a small subset. I bet my test builds hit the failure
because I have some library installed on my build servers that
isn't installed on Linaro's servers.

This is why I can't cross-build perf; my cross build environments
don't have the necessary libraries installed.

Guenter