From: Thomas Hellstrom <thomas@shipmail.org>
To: Thomas Hellstrom <thellstrom@vmware.com>,
airlied@gmail.com, daniel.vetter@ffwll.ch
Cc: pv-drivers@vmware.com, linux-graphics-maintainer@vmware.com,
dri-devel@lists.freedesktop.org
Subject: Re: [git pull] vmwgfx-fixes-5.0-190130
Date: Wed, 30 Jan 2019 20:37:33 +0100 [thread overview]
Message-ID: <d3319663-e325-6144-e7a2-340e7d7ce922@shipmail.org> (raw)
In-Reply-To: <20190130105531.61599-1-thellstrom@vmware.com>
Hi,
On 1/30/19 11:55 AM, Thomas Hellstrom wrote:
> Dave, Daniel
>
> A fix for a DMA API change from Christoph Hellwig for vmwgfx, and
> Two stable fixes for regressions in the vmwgfx driver
>
> The following changes since commit f0e7ce1eef5854584dfb59b3824a67edee37580f:
>
> Merge tag 'drm-msm-fixes-2019-01-24' of git://people.freedesktop.org/~robclark/linux into drm-fixes (2019-01-25 07:45:00 +1000)
>
> are available in the Git repository at:
>
> git://people.freedesktop.org/~thomash/linux tags/vmwgfx-fixes-5.0-190130
>
> for you to fetch changes up to 46984feb928ade4af744eb4e4cc8b242ffaf14e3:
>
> drm/vmwgfx: Also check for crtc status while checking for DU active (2019-01-29 13:57:56 +0100)
>
Please ignore this pull request. I got notified about an uninitialized
variable warning which looks false, but since they typically aren't
false I'd like to investigate further. In any case I don't want to
introduce that warning message in a stable patch.
Thanks,
Thomas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-01-30 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 10:55 [git pull] vmwgfx-fixes-5.0-190130 Thomas Hellstrom
2019-01-30 19:37 ` Thomas Hellstrom [this message]
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=d3319663-e325-6144-e7a2-340e7d7ce922@shipmail.org \
--to=thomas@shipmail.org \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=pv-drivers@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