From: Borislav Petkov <bp@suse.de>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: LKP <lkp@01.org>, lkml <linux-kernel@vger.kernel.org>,
Ye Xiaolong <xiaolong.ye@intel.com>,
Philip Li <philip.li@intel.com>,
Huang Ying <ying.huang@intel.com>
Subject: Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040
Date: Mon, 20 Feb 2017 10:35:51 +0100 [thread overview]
Message-ID: <20170220093551.crucsscnh5zvd2si@pd.tnic> (raw)
In-Reply-To: <20170220030352.fksjiy6ktuxwtvdg@wfg-t540p.sh.intel.com>
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)
--
next prev parent reply other threads:[~2017-02-20 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170218050153.wc7zhrtv5q5wjszq@wfg-t540p.sh.intel.com>
2017-02-18 14:48 ` [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 Borislav Petkov
2017-02-18 23:29 ` Fengguang Wu
2017-02-19 0:10 ` Borislav Petkov
2017-02-19 1:06 ` Fengguang Wu
2017-02-19 13:50 ` Borislav Petkov
2017-02-20 3:03 ` Fengguang Wu
2017-02-20 9:35 ` Borislav Petkov [this message]
2017-02-21 0:00 ` email/patch test requests to 0day robot Fengguang Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170220093551.crucsscnh5zvd2si@pd.tnic \
--to=bp@suse.de \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=philip.li@intel.com \
--cc=xiaolong.ye@intel.com \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox