dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: David Airlie <airlied@redhat.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: [PULL] drm-qemu: 4.10 updates
Date: Tue, 10 Jan 2017 15:55:09 +0100	[thread overview]
Message-ID: <1484060109.19018.121.camel@redhat.com> (raw)

  Hi,

Sorry, I'm a little late for the 4.10 merge window (too busy with other
stuff in december).  The only code change in this pull is a one-line
sparse fix for virtio-gpu though, the other changes are docs only.  So I
think it should be fine for 4.10 at this point.  If you disagree feel
free to queue up for 4.11 instead.

thanks,
  Gerd

The following changes since commit
a121103c922847ba5010819a3f250f1f7fc84ab8:

  Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)

are available in the git repository at:

  git://git.kraxel.org/linux tags/drm-qemu-20170110

for you to fetch changes up to af3076e67c31ceb3e314933dd61cb68a1d5120cf:

  drm: flip cirrus driver status to "obsolete". (2017-01-10 14:00:40
+0100)

----------------------------------------------------------------
drm-qemu: virtio sparse fix, MAINTAINERS updates.

----------------------------------------------------------------
Gerd Hoffmann (3):
      drm/virtio: fix framebuffer sparse warning
      drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl,
virtio-gpu)
      drm: flip cirrus driver status to "obsolete".

 MAINTAINERS                         | 16 +++++++++++++---
 drivers/gpu/drm/cirrus/Kconfig      |  9 +++++++++
 drivers/gpu/drm/virtio/virtgpu_fb.c |  2 +-
 3 files changed, 23 insertions(+), 4 deletions(-)

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

                 reply	other threads:[~2017-01-10 14:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1484060109.19018.121.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=airlied@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox