[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191127205400.cip7hdbhcdokofel@rric.localdomain>
Date: Wed, 27 Nov 2019 20:54:10 +0000
From: Robert Richter <rrichter@...vell.com>
To: John Garry <john.garry@...wei.com>
CC: Borislav Petkov <bp@...en8.de>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
James Morse <james.morse@....com>,
"tony.luck@...el.com" <tony.luck@...el.com>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
wanghuiqiang <wanghuiqiang@...wei.com>,
Xiaofei Tan <tanxiaofei@...wei.com>,
Linuxarm <linuxarm@...wei.com>,
"Huangming (Mark)" <huangming23@...wei.com>
Subject: Re: linuxnext-2019127 edac warns (was Re: edac KASAN warning in
experimental arm64 allmodconfig boot)
Hi John,
thank you for testing.
On 27.11.19 17:07:33, John Garry wrote:
> [snip]
>
> I have test enabled:
> +CONFIG_DEBUG_TEST_DRIVER_REMOVE=y
> +CONFIG_KASAN=y
> +CONFIG_DEBUG_KMEMLEAK=y
Is this a regression (did it work before?), or a new test that you
newly run?
Thanks,
-Robert
Powered by blists - more mailing lists