From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752343AbdBTKNo (ORCPT ); Mon, 20 Feb 2017 05:13:44 -0500 Received: from mx2.suse.de ([195.135.220.15]:55859 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751041AbdBTKNm (ORCPT ); Mon, 20 Feb 2017 05:13:42 -0500 Date: Mon, 20 Feb 2017 10:35:51 +0100 From: Borislav Petkov To: Fengguang Wu Cc: LKP , lkml , Ye Xiaolong , Philip Li , Huang Ying Subject: Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 Message-ID: <20170220093551.crucsscnh5zvd2si@pd.tnic> References: <20170218050153.wc7zhrtv5q5wjszq@wfg-t540p.sh.intel.com> <20170218144759.bqdy3ugj45uh36zc@pd.tnic> <20170218232950.picqhk2xlmx3uh4l@wfg-t540p.sh.intel.com> <20170219001047.ivdkkkmrml6bh5v3@pd.tnic> <20170219010651.nsxugr7j6exvh3wn@wfg-t540p.sh.intel.com> <20170219135019.tiaed3zl5t5vr45k@pd.tnic> <20170220030352.fksjiy6ktuxwtvdg@wfg-t540p.sh.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20170220030352.fksjiy6ktuxwtvdg@wfg-t540p.sh.intel.com> User-Agent: NeoMutt/20161014 (1.7.1) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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) --