From: Thomas Gleixner <tglx@linutronix.de>
To: Philip Li <philip.li@intel.com>
Cc: Borislav Petkov <bp@suse.de>, kbuild test robot <lkp@intel.com>,
linux-input@vger.kernel.org,
Thomas Hellstrom <thellstrom@vmware.com>, x86-ml <x86@kernel.org>,
linux-tip-commits@vger.kernel.org, pv-drivers@vmware.com,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org,
tip-bot2 for Thomas Hellstrom <tip-bot2@linutronix.de>,
Doug Covelli <dcovelli@vmware.com>,
Ingo Molnar <mingo@redhat.com>,
VMware Graphics <linux-graphics-maintainer@vmware.com>,
kbuild-all@01.org, "H. Peter Anvin" <hpa@zytor.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions
Date: Fri, 30 Aug 2019 08:06:27 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908300802390.1938@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190830010349.GD857@intel.com>
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
next prev parent reply other threads:[~2019-08-30 6:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 8:03 [PATCH v3 0/4] Add support for updated vmware hypercall instruction Thomas Hellström (VMware)
2019-08-28 8:03 ` [PATCH v3 1/4] x86/vmware: Update platform detection code for VMCALL/VMMCALL hypercalls Thomas Hellström (VMware)
2019-08-28 13:30 ` [tip: x86/vmware] " tip-bot2 for Thomas Hellstrom
2019-08-28 8:03 ` [PATCH v3 2/4] x86/vmware: Add a header file for hypercall definitions Thomas Hellström (VMware)
2019-08-28 13:30 ` [tip: x86/vmware] " tip-bot2 for Thomas Hellstrom
2019-08-28 8:03 ` [PATCH v3 3/4] drm/vmwgfx: Update the backdoor call with support for new instructions Thomas Hellström (VMware)
2019-08-28 13:30 ` [tip: x86/vmware] " tip-bot2 for Thomas Hellstrom
2019-08-28 8:03 ` [PATCH v3 4/4] input/vmmouse: " Thomas Hellström (VMware)
2019-08-28 13:30 ` [tip: x86/vmware] " tip-bot2 for Thomas Hellstrom
2019-08-29 16:01 ` kbuild test robot
2019-08-29 16:33 ` Borislav Petkov
2019-08-30 1:03 ` [kbuild-all] " Philip Li
2019-08-30 6:06 ` Thomas Gleixner [this message]
2019-08-30 6:20 ` Philip Li
2019-08-30 6:33 ` Philip Li
2019-08-30 7:58 ` Thomas Gleixner
2019-08-30 8:06 ` Borislav Petkov
2019-08-30 14:36 ` Philip Li
2019-08-30 14:46 ` Borislav Petkov
2019-08-30 15:00 ` Philip Li
2019-08-30 15:06 ` Borislav Petkov
2019-08-30 15:26 ` Philip Li
2019-08-30 15:08 ` Philip Li
2019-08-30 19:35 ` Borislav Petkov
2019-09-02 1:13 ` Philip Li
2019-09-02 9:36 ` Borislav Petkov
2019-09-03 1:06 ` Philip Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1908300802390.1938@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@suse.de \
--cc=dcovelli@vmware.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=philip.li@intel.com \
--cc=pv-drivers@vmware.com \
--cc=thellstrom@vmware.com \
--cc=tip-bot2@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).