From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754217AbbJGNor (ORCPT ); Wed, 7 Oct 2015 09:44:47 -0400 Received: from mga09.intel.com ([134.134.136.24]:57242 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753092AbbJGNoq (ORCPT ); Wed, 7 Oct 2015 09:44:46 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,649,1437462000"; d="scan'208";a="786670043" Date: Wed, 7 Oct 2015 21:44:32 +0800 From: Fengguang Wu To: Peter Zijlstra Cc: bobby prani , Thomas Gleixner , oleg@redhat.com, fweisbec@gmail.com, dvhart@linux.intel.com, Lai Jiangshan , linux-kernel@vger.kernel.org, rostedt , josh@joshtriplett.org, dhowells@redhat.com, edumazet@google.com, Mathieu Desnoyers , kbuild-all@01.org, dipankar@in.ibm.com, Andrew Morton , "Paul E. McKenney" , Ingo Molnar Subject: Re: [kbuild-all] [PATCH tip/core/rcu 02/18] rcu: Move rcu_report_exp_rnp() to allow consolidation Message-ID: <20151007134432.GA15834@wfg-t540p.sh.intel.com> References: <20151007115046.GK11639@twins.programming.kicks-ass.net> <201510072021.GNkjQ4uR%fengguang.wu@intel.com> <20151007121751.GG17308@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151007121751.GG17308@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 07, 2015 at 02:17:51PM +0200, Peter Zijlstra wrote: > On Wed, Oct 07, 2015 at 08:11:01PM +0800, kbuild test robot wrote: > > Hi Peter, > > > > [auto build test WARNING on v4.3-rc4 -- if it's inappropriate base, please ignore] > > So much punishment for not having compiled my proto patch :/ > > Wu, is there a tag one can include to ward off this patch sucking robot > prematurely? Yes. The best way may be to push the patches to a git tree known to 0day robot: https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/tree/repo/linux So that it's tested first there. You'll then get private email reports if it's a private git branch. The robot has logic to avoid duplicate testing an emailed patch (based on patch-id and author/title) if its git tree version has been tested. We may also add a rule: only send private reports for patches with "RFC", "Not-yet-signed-off-by:", etc. Thanks, Fengguang