From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AA207C3A5A3 for ; Fri, 30 Aug 2019 06:06:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7235621670 for ; Fri, 30 Aug 2019 06:06:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727562AbfH3GGd (ORCPT ); Fri, 30 Aug 2019 02:06:33 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:52250 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726920AbfH3GGd (ORCPT ); Fri, 30 Aug 2019 02:06:33 -0400 Received: from p5de0b6c5.dip0.t-ipconnect.de ([93.224.182.197] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1i3a3I-00057o-9x; Fri, 30 Aug 2019 08:06:28 +0200 Date: Fri, 30 Aug 2019 08:06:27 +0200 (CEST) From: Thomas Gleixner To: Philip Li cc: Borislav Petkov , kbuild test robot , linux-input@vger.kernel.org, Thomas Hellstrom , x86-ml , linux-tip-commits@vger.kernel.org, pv-drivers@vmware.com, Dmitry Torokhov , linux-kernel@vger.kernel.org, tip-bot2 for Thomas Hellstrom , Doug Covelli , Ingo Molnar , VMware Graphics , kbuild-all@01.org, "H. Peter Anvin" , Ingo Molnar Subject: Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions In-Reply-To: <20190830010349.GD857@intel.com> Message-ID: References: <156699905611.5321.15444519862547054670.tip-bot2@tip-bot2> <201908292325.aLXyyzEx%lkp@intel.com> <20190829163353.GC2132@zn.tnic> <20190830010349.GD857@intel.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Philip, On Fri, 30 Aug 2019, Philip Li wrote: > > wanna test trees, I'd suggest simply testing TIP's tip/master branch > > which gets redone on a daily basis instead of testing patches in the > > tip-bot{,2} notification mails. > > Thanks Boris for the input. Besides the repo monitoring, we also check the patches > in mailing lists, and try to apply patch to a suitable base. Do you think we can > skip the mailing list of tip-bot{,2}? As I just explained in a reply to another random build failure caused by this. tip-bot2 is a notification mechanism to let people know that a particular patch has been merged into one of the tip tree branches. These mails are also properly threaded most of the time and reply to the patch which was sent to the mailing list. So yes, randomly picking patches from tip-bot2 is not useful at all. The mails contain the information to which tip branch the patch has been applied, so the only useful information for your bot is to select the branch which got the new patches and start testing on that one. Thanks, tglx