From: Thomas Hellstrom <thellstrom@vmware.com>
To: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] vmwgfx-next-2018-12-13
Date: Wed, 6 Feb 2019 19:46:13 +0000 [thread overview]
Message-ID: <096463dd4ae68c4f3783d1fab070d9138649af9f.camel@vmware.com> (raw)
In-Reply-To: <20190206194253.4582-1-thellstrom@vmware.com>
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: Use the standard atomic helpers for page-flip (2018-12-
> 05 10:09:55 +0100)
>
> are available in the Git repository at:
>
> git://people.freedesktop.org/~thomash/linux tags/vmwgfx-next-2018-
> 12-13
>
> for you to fetch changes up to
> 0660d8cd83938ef5cc91582fe6f951e8935f2d0f:
>
> drm: Fix docs warning in drm_damage_helper.c (2018-12-11 15:20:13
> +0100)
>
> ----------------------------------------------------------------
> Pull request of 2018-12-13
>
> ----------------------------------------------------------------
> Colin Ian King (1):
> drm/selftest: fix spelling mistake "dimention" -> "dimension"
>
> Deepak Rawat (1):
> drm: Fix docs warning in drm_damage_helper.c
>
> drivers/gpu/drm/drm_damage_helper.c | 2 +-
> drivers/gpu/drm/selftests/test-drm_damage_helper.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-02-06 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 19:42 [git pull] vmwgfx-next-2018-12-13 Thomas Hellstrom
2019-02-06 19:46 ` Thomas Hellstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-13 13:08 Thomas Hellstrom
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=096463dd4ae68c4f3783d1fab070d9138649af9f.camel@vmware.com \
--to=thellstrom@vmware.com \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.