[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170220093551.crucsscnh5zvd2si@pd.tnic>
Date: Mon, 20 Feb 2017 10:35:51 +0100
From: Borislav Petkov <bp@...e.de>
To: Fengguang Wu <fengguang.wu@...el.com>
Cc: LKP <lkp@...org>, lkml <linux-kernel@...r.kernel.org>,
Ye Xiaolong <xiaolong.ye@...el.com>,
Philip Li <philip.li@...el.com>,
Huang Ying <ying.huang@...el.com>
Subject: Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL
pointer dereference at 0000000000000040
On Mon, Feb 20, 2017 at 11:03:52AM +0800, Fengguang Wu wrote:
> We actually already test LKML patch in that way (Xiaolong maintains
> this feature). Nevertheless if developers specify "base-commit:" it
> could help eliminate the guessing works by the dumb robot. We'll
> appreciate if the "base-commit:" or "base-patchid:" tags are listed
> in the patches, especially in some non-obvious situations.
Can I specify multiple base commits for testing stable backports?
For example
base-commit: v4.9.11, v4.4.50, v3.10.105,...
> Such tags could be regarded as "explicit" test requests, where we could
> send "BUILD COMPLETE" emails as a response (comparing to our normal
> LKML patch tests, which only build regressions will trigger an email
> notification).
Yap, similar to those you guys sent when a new branch on k.org has been
tested.
Btw, can we make the format layout this way:
patch
---
<0day bot tags>
---
so that when we send it to lkml, it doesn't interfere with review by
slapping the tags at the beginning of the patch?
Also, should we CC some special mailing list which the 0day bot parses
or lkml is enough?
Cool stuff.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
Powered by blists - more mailing lists