Re: [git pull] vmwgfx-next

2020-01-21 Thread VMware
On 1/20/20 10:09 PM, Dave Airlie wrote: On Thu, 16 Jan 2020 at 19:30, Thomas Hellström (VMware) wrote: Dave, Daniel The main 5.6 -next pull from vmwgfx. Minor things here and there, as well as an added ioctl for host messaging and a corresponding api version bump. Is there userspace for this

Re: [git pull] vmwgfx-next

2020-01-20 Thread VMware
On 1/20/20 10:09 PM, Dave Airlie wrote: On Thu, 16 Jan 2020 at 19:30, Thomas Hellström (VMware) wrote: Dave, Daniel The main 5.6 -next pull from vmwgfx. Minor things here and there, as well as an added ioctl for host messaging and a corresponding api version bump. Is there userspace for this

Re: [git pull] vmwgfx-next

2020-01-20 Thread Dave Airlie
On Thu, 16 Jan 2020 at 19:30, Thomas Hellström (VMware) wrote: > > Dave, Daniel > > The main 5.6 -next pull from vmwgfx. Minor things here and there, as well > as an added ioctl for host messaging and a corresponding api version bump. Is there userspace for this ioctl somewhere? I need a pointer

Re: [git pull] vmwgfx-next

2019-08-14 Thread VMware
On 8/14/19 9:31 AM, Thomas Hellström (VMware) wrote: From: Thomas Hellstrom (VMware) Dave, Daniel A couple of independent patches extracted from the 5.3 pull request, fixed for merge conflicts. Hmm. Just noted an unused variable resulting from one of the commits. Please ignore this for now,

Re: [git pull] vmwgfx-next-2018-12-13

2019-02-06 Thread Thomas Hellstrom
Old pull message. Please ignore. The correct one coming up. /Thomas On Wed, 2019-02-06 at 20:42 +0100, Thomas Hellstrom wrote: > Hi, Dave > > Two minor fixes for the previous vmwgfx-next pull: > > The following changes since commit > 9a01135b98b9d5a7033c544245da7aad0d886758: > > drm/vmwgfx

Re: [Git PULL] vmwgfx-next

2017-08-28 Thread Sinclair Yeh
On Tue, Aug 29, 2017 at 06:35:38AM +1000, Dave Airlie wrote: > On 29 August 2017 at 06:22, Sinclair Yeh wrote: > > Hi Dave, > > > > The following changes since commit 7c0059dd832cc686bf0febefdcf8295cdd93007f: > > Just a reminder, -next branches need to be sent before rc6 if you want > them in the

Re: [Git PULL] vmwgfx-next

2017-08-28 Thread Dave Airlie
On 29 August 2017 at 06:22, Sinclair Yeh wrote: > Hi Dave, > > The following changes since commit 7c0059dd832cc686bf0febefdcf8295cdd93007f: Just a reminder, -next branches need to be sent before rc6 if you want them in the next kernel. I'll take a look at this branch later since it's pretty late

Re: [git pull] vmwgfx-next

2017-04-03 Thread Sinclair Yeh
On Sun, Apr 02, 2017 at 08:11:12PM +0200, Daniel Vetter wrote: > On Fri, Mar 31, 2017 at 04:32:55PM -0700, Sinclair Yeh wrote: > > Hi Dave, > > > > This series enables atomic mode set for vmwgfx. A number of features and > > larger fixes are also included. > > > > The following changes since com

Re: [git pull] vmwgfx-next

2017-04-02 Thread Daniel Vetter
On Fri, Mar 31, 2017 at 04:32:55PM -0700, Sinclair Yeh wrote: > Hi Dave, > > This series enables atomic mode set for vmwgfx. A number of features and > larger fixes are also included. > > The following changes since commit 8cd3ac52963f2e99f4c21d1c9ce89531ce66c2d6: > > Merge branch 'drm-next-4