[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180522140203.GA7374@kroah.com>
Date: Tue, 22 May 2018 16:02:03 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>,
open list <linux-kernel@...r.kernel.org>,
Shuah Khan <shuah@...nel.org>, patches@...nelci.org,
lkft-triage@...ts.linaro.org,
Ben Hutchings <ben.hutchings@...ethink.co.uk>,
linux- stable <stable@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Guenter Roeck <linux@...ck-us.net>
Subject: Re: [PATCH 4.16 000/110] 4.16.11-stable review
On Tue, May 22, 2018 at 07:54:44AM -0500, Dan Rue wrote:
> On Tue, May 22, 2018 at 04:18:31PM +0530, Naresh Kamboju wrote:
> > On 22 May 2018 at 02:40, Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> > > This is the start of the stable review cycle for the 4.16.11 release.
> > > There are 110 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.
> > >
> > > Responses should be made by Tue May 22 21:04:14 UTC 2018.
> > > Anything received after that time might be too late.
> > >
> > > The whole patch series can be found in one patch at:
> > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.16.11-rc1.gz
> > > or in the git tree and branch at:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.16.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > Results from Linaro’s test farm.
> > No regressions on arm64, arm and x86_64.
> >
> > NOTE:
> > kselftest rtnetlink.sh test case failed on all devices.
> > Which is not a regression which used to SKIP pass and now run and fail.
> > Bug reported to investigate,
> > https://bugs.linaro.org/show_bug.cgi?id=3834
>
> To clarify - previously rtnetlink.sh did not run because we were missing
> the 'tc' command in our rootfs. We added it recently, and now the test
> runs and fails, likely due to a missing kernel config.
Thanks for clarifying this, it makes more sense now.
Hopefully you all can fix that kernel config one day :)
thanks,
greg k-h
Powered by blists - more mailing lists