From: m.t@ox.io
To: Thomas Hellstrom <thellstrom@vmware.com>, linux-kernel@vger.kernel.org
Cc: Sinclair Yeh <syeh@vmware.com>,
linux-graphics-maintainer@vmware.com,
dri-devel@lists.freedesktop.org
Subject: Re: [Linux-graphics-maintainer] No mouse cursor since 36cc79bc9077319c04bd3b132edcacaa9a0d9f2b
Date: Wed, 10 May 2017 12:31:39 +0200 (CEST) [thread overview]
Message-ID: <975768186.627.1494412299617@app.ox.io> (raw)
In-Reply-To: <d494f377-4c79-412d-6e58-56126273955a@vmware.com>
> Thomas Hellstrom hat am 10. Mai 2017 um 10:35 geschrieben:
>
> Hi,
>
> Thanks for reporting.
I would have reported earlier if it had not taken 3 days on the vm to bisect.
> I think there is a fix for this either in preparation or queued for
> submission. Sinclair (CC'd) should know more.
If you point me to a patch I can test it.
> Thanks,
> Thomas
Mark
>
> On 05/10/2017 09:17 AM, m.t wrote:
> > Hi,
> > I don't have a mouse cursor in my virtual machine (vmware workstation 12.5.5
> > build-5234757) with latest master from https://urldefense.proofpoint.com/v2/url?u=https-3A__git.kernel.org_pub_scm_linux_&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=j2ey7nuAQ5d6NbMmCOnRsTIJfmv7blo3UCKagbsM9o2-No8JdlhkKK3ty481ErVu&m=DWnNRbcrxMhc78PIvembLdV3OsJi3vPwcdG03kqVpJo&s=mc7-KF2t4BktXs11MShGZBf9bzgxumqhmVQ0ocAIS0k&e=
> > kernel/git/torvalds/linux.git
> >
> > git bisect led me to 36cc79bc9077319c04bd3b132edcacaa9a0d9f2b as culprit.
> >
> > Regards
> > Mark
> > _______________________________________________
> > Sent to linux-graphics-maintainer@vmware.com
>
>
next prev parent reply other threads:[~2017-05-10 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 7:17 m.t
[not found] ` <d494f377-4c79-412d-6e58-56126273955a@vmware.com>
2017-05-10 10:31 ` m.t [this message]
2017-05-10 16:46 ` [Linux-graphics-maintainer] " Sinclair Yeh
2017-05-11 5:38 ` m.t
2017-06-01 5:33 ` m.t
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=975768186.627.1494412299617@app.ox.io \
--to=m.t@ox.io \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syeh@vmware.com \
--cc=thellstrom@vmware.com \
/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
all inboxes | Powered by JetHome®