[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7hingmdz2d.fsf@baylibre.com>
Date: Wed, 13 Sep 2017 15:16:26 -0700
From: Kevin Hilman <khilman@...libre.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: "kernelci.org bot" <bot@...nelci.org>,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net,
shuahkh@....samsung.com, patches@...nelci.org,
ben.hutchings@...ethink.co.uk, stable@...r.kernel.org
Subject: Re: [PATCH 4.13 00/27] 4.13.2-stable review
Greg Kroah-Hartman <gregkh@...uxfoundation.org> writes:
> On Tue, Sep 12, 2017 at 03:57:50PM -0700, kernelci.org bot wrote:
>> stable-rc/linux-4.13.y boot: 210 boots: 7 failed, 200 passed with 3 conflicts (v4.13.1-28-g0a9a7505477b)
>
> 7 failures here, and 8 for 4.12, are these to be expected?
They are expected in the sense that nobody seems to care about the
defconfigs that are failing, so nobody is looking into the failures.
Since almost all of these failures seem to be related to various
defconfnig + kconfig-fragment builds that nobody is taking the time to
fix, I'm going reduce the set of defconfig that are built for stable
trees to just the in-tree defconfigs.
That should greatly reduce the signal-to-noise for these stable
reports. We can then add back defconfigs as needed, on the condition
that someone has the time/energy to keep those configs working in stable
trees.
Kevin
Powered by blists - more mailing lists