Re: [kbuild-all] [PATCH tip/core/rcu 02/18] rcu: Move rcu_report_exp_rnp() to allow consolidation

[Fengguang Wu]

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/