Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions
- From: Philip Li <philip.li@xxxxxxxxx>
- Date: Fri, 30 Aug 2019 22:36:45 +0800
- Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx>, kbuild test robot <lkp@xxxxxxxxx>, linux-input@xxxxxxxxxxxxxxx, Thomas Hellstrom <thellstrom@xxxxxxxxxx>, x86-ml <x86@xxxxxxxxxx>, linux-tip-commits@xxxxxxxxxxxxxxx, pv-drivers@xxxxxxxxxx, Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, tip-bot2 for Thomas Hellstrom <tip-bot2@xxxxxxxxxxxxx>, Doug Covelli <dcovelli@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, VMware Graphics <linux-graphics-maintainer@xxxxxxxxxx>, kbuild-all@xxxxxx, "H. Peter Anvin" <hpa@xxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>
- In-reply-to: <20190830080650.GA30413@zn.tnic>
- References: <156699905611.5321.15444519862547054670.tip-bot2@tip-bot2> <201908292325.aLXyyzEx%lkp@intel.com> <20190829163353.GC2132@zn.tnic> <20190830010349.GD857@intel.com> <alpine.DEB.2.21.1908300802390.1938@nanos.tec.linutronix.de> <20190830062053.GA2598@intel.com> <20190830080650.GA30413@zn.tnic>
- User-agent: Mutt/1.9.4 (2018-02-28)
On Fri, Aug 30, 2019 at 10:06:50AM +0200, Borislav Petkov wrote:
> On Fri, Aug 30, 2019 at 02:20:53PM +0800, Philip Li wrote:
> > thanks for your patience. I just realize we actually block tip-bot, but
> > not tip-bot2. I will update the logic to avoid this issue, and we will
> > keep monitor for a while to fix new issue if any.
>
> ... and just to reiterate: it would be a *lot-lot* more useful if you
> guys tested the single tip branches or the combined tip/master on a
> daily basis as that is the x86 queue that goes to Linus eventually. That
yes, we monitor the repo pub/scm/linux/kernel/git/tip/tip.git, and will
send build status of head (like BUILD SUCCESS or REGRESSION), also provide
bisect report of unique error for first bad commit.
> is, if you do not test it already. But we don't get any "we tested this
> branch" email so I'm thinking you don't...
>
> Thx.
>
> --
> Regards/Gruss,
> Boris.
>
> Good mailing practices for 400: avoid top-posting and trim the reply.
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]