From: "Thomas Hellström (VMware)" <thomas@shipmail.org>
To: airlied@gmail.com, daniel@ffwll.ch, dri-devel@lists.freedesktop.org
Cc: pv-drivers@vmware.com, linux-graphics-maintainer@vmware.com
Subject: Re: [git pull] vmwgfx-next
Date: Wed, 14 Aug 2019 19:35:48 +0200 [thread overview]
Message-ID: <7c51e197-c80a-136c-c893-2db8c96c0904@shipmail.org> (raw)
In-Reply-To: <20190814073152.3120-1-thomas@shipmail.org>
On 8/14/19 9:31 AM, Thomas Hellström (VMware) wrote:
> From: Thomas Hellstrom (VMware) <thomas@shipmail.org>
>
> 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, and I'll do a quick respin.
/Thomas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next parent reply other threads:[~2019-08-14 17:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190814073152.3120-1-thomas@shipmail.org>
2019-08-14 17:35 ` Thomas Hellström (VMware) [this message]
2020-01-16 9:29 [git pull] vmwgfx-next Thomas Hellström (VMware)
2020-01-20 21:09 ` Dave Airlie
2020-01-20 21:42 ` Thomas Hellström (VMware)
2020-01-21 9:49 ` Thomas Hellström (VMware)
-- strict thread matches above, loose matches on Subject: below --
2019-11-14 13:17 Thomas Hellström (VMware)
2019-08-15 7:15 Thomas Hellström (VMware)
2019-06-19 7:25 Thomas Hellström (VMware)
2018-12-05 10:35 Thomas Hellstrom
2018-09-28 13:11 Thomas Hellstrom
2017-08-28 20:22 [Git PULL] vmwgfx-next Sinclair Yeh
2017-08-28 20:35 ` Dave Airlie
2017-08-28 20:39 ` Sinclair Yeh
2017-04-21 17:18 [git pull] vmwgfx-next Sinclair Yeh
2017-03-31 23:32 Sinclair Yeh
2017-04-02 18:11 ` Daniel Vetter
2017-04-03 19:00 ` Sinclair Yeh
2017-01-30 19:46 Sinclair Yeh
2015-11-06 15:29 Thomas Hellstrom
2015-11-02 8:23 Thomas Hellstrom
2015-08-06 12:54 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=7c51e197-c80a-136c-c893-2db8c96c0904@shipmail.org \
--to=thomas@shipmail.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=pv-drivers@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 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.