On Mon, Oct 08, 2018 at 12:48:41PM -0500, Rob Herring wrote:
On Sun, Oct 7, 2018 at 9:19 AM Guenter Roeck linux@roeck-us.net wrote:
On Wed, Oct 03, 2018 at 11:08:47AM -0700, Guenter Roeck wrote:
On Wed, Oct 03, 2018 at 12:53:11PM -0500, Rob Herring wrote:
On Wed, Oct 3, 2018 at 12:24 PM Guenter Roeck linux@roeck-us.net wrote:
On Wed, Oct 03, 2018 at 09:25:39AM -0700, Greg Kroah-Hartman wrote:
On Wed, Oct 03, 2018 at 05:59:09AM -0700, Guenter Roeck wrote: > On 10/02/2018 06:21 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.18.12 release. > > There are 228 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 Thu Oct 4 13:24:08 UTC 2018. > > Anything received after that time might be too late. > > > > > > Build results: > total: 137 pass: 137 fail: 0 > Qemu test results: > total: 321 pass: 320 fail: 1 > Failed tests: > powerpc:g3beige:ppc_book3s_defconfig:nosmp:ide:rootfs
What is the status of that powerpc failure fix? What's the odds it can get into mainline soon?
The fix has been -next for about a week.
da08d8cb8cfc of: unittest: Disable interrupt node tests for old world MAC systems
You'll have to ask Rob (copied) if he plans to send a pull request before the next commit window opens.
I wasn't planning to as it's just for the unittest and has been that way for how long? Why's the unittest enabled for a defconfig anyways?
I enabled it to improve test coverage for stable releases. This is how I found the problem in the first place. Are you suggesting that I should not run DT unit tests for stable release candidates ?
I have now disabled CONFIG_OF_UNITTEST in my tests.
Well no, that wasn't what I was suggesting. I'll send it to Greg this week.
Are there details on how you run qemu?
Official ? No.
However, everything is published at https://github.com/groeck/linux-build-test/.
Guenter