From: Philip Li <philip.li@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.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 23:00:02 +0800 [thread overview]
Message-ID: <20190830150002.GA6931@intel.com> (raw)
In-Reply-To: <20190830144628.GC30413@zn.tnic>
On Fri, Aug 30, 2019 at 04:46:28PM +0200, Borislav Petkov wrote:
> On Fri, Aug 30, 2019 at 10:36:45PM +0800, Philip Li wrote:
> > yes, we monitor the repo pub/scm/linux/kernel/git/tip/tip.git, and will
> > send build status of head
>
> ... and what you call "head" is the "master" branch on that repo, right?
Hi Boris, you are right. It is the head of monitored branch, here master branch is
one of the branches on this repo that we monitor.
Early on, there's requirement to blacklist a few branches, which is configured
as below
blacklist_branch: auto-.*|tmp-.*|base-.*|test.*|.*-for-linus
Except the blacklist branches, we will monitor all other branches. We also
support pull request to update the configuration or email us to update.
Refer to https://github.com/intel/lkp-tests/blob/master/repo/linux/tip.
Thanks
> Just making sure you got that right.
>
> > (like BUILD SUCCESS or REGRESSION), also provide bisect report of
> > unique error for first bad commit.
>
> Perfect!
>
> Thx.
>
> --
> Regards/Gruss,
> Boris.
>
> Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-08-30 15:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190828080353.12658-5-thomas_os@shipmail.org>
2019-08-28 13:30 ` [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions 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
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 [this message]
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=20190830150002.GA6931@intel.com \
--to=philip.li@intel.com \
--cc=bp@alien8.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=pv-drivers@vmware.com \
--cc=tglx@linutronix.de \
--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).