From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754544AbbJGNzn (ORCPT <rfc822;w@1wt.eu>);
	Wed, 7 Oct 2015 09:55:43 -0400
Received: from bombadil.infradead.org ([198.137.202.9]:60991 "EHLO
	bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754251AbbJGNzm (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 7 Oct 2015 09:55:42 -0400
Date: Wed, 7 Oct 2015 15:55:29 +0200
From: Peter Zijlstra <peterz@infradead.org>
To: Fengguang Wu <lkp@intel.com>
Cc: bobby prani <bobby.prani@gmail.com>, Thomas Gleixner <tglx@linutronix.de>,
        oleg@redhat.com, fweisbec@gmail.com, dvhart@linux.intel.com,
        Lai Jiangshan <jiangshanlai@gmail.com>, linux-kernel@vger.kernel.org,
        rostedt <rostedt@goodmis.org>, josh@joshtriplett.org,
        dhowells@redhat.com, edumazet@google.com,
        Mathieu Desnoyers <mathieu.desnoyers@efficios.com>, kbuild-all@01.org,
        dipankar@in.ibm.com, Andrew Morton <akpm@linux-foundation.org>,
        "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
        Ingo Molnar <mingo@kernel.org>
Subject: Re: [kbuild-all] [PATCH tip/core/rcu 02/18] rcu: Move
 rcu_report_exp_rnp() to allow consolidation
Message-ID: <20151007135529.GG3816@twins.programming.kicks-ass.net>
References: <20151007115046.GK11639@twins.programming.kicks-ass.net>
 <201510072021.GNkjQ4uR%fengguang.wu@intel.com>
 <20151007121751.GG17308@twins.programming.kicks-ass.net>
 <20151007134432.GA15834@wfg-t540p.sh.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20151007134432.GA15834@wfg-t540p.sh.intel.com>
User-Agent: Mutt/1.5.21 (2012-12-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Oct 07, 2015 at 09:44:32PM +0800, Fengguang Wu wrote:

> > 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.

Right, but if I can't be bothered to compile test a patch, I also cannot
be bothered to stuff it into git :-)

> We may also add a rule: only send private reports for patches with
> "RFC", "Not-yet-signed-off-by:", etc.

How about not building when there's no "^Signed-off-by:" at all?

Even private build fails for patches like this -- esp. 3+ -- gets
annoying real quick.

Also note that this 'patch' has: $subject ~ /^Re:/, nor did it have
"^Subject:" like headers in the body.