dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: michel@daenzer.net, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 0/5] drm: more byteorder fixes
Date: Fri, 21 Sep 2018 11:40:48 +0200	[thread overview]
Message-ID: <20180921094048.GF11082@phenom.ffwll.local> (raw)
In-Reply-To: <20180919111252.7932-1-kraxel@redhat.com>

On Wed, Sep 19, 2018 at 01:12:47PM +0200, Gerd Hoffmann wrote:
> Fix fbdev emulation.
> Fix bochs-drm and virtio-gpu drivers.
> 
> Gerd Hoffmann (5):
>   drm: move native byte order quirk to new drm_mode_legacy_fb_format2
>     function
>   drm: use drm_mode_legacy_fb_format2 in drm_gem_fbdev_fb_create
>   drm/bochs: fix DRM_FORMAT_* handling for big endian machines.
>   drm/bochs: support changing byteorder at mode set time
>   drm/virtio: fix DRM_FORMAT_* handling

Aside from the "naming is hard" nit, series looks good. With the naming
figured out somehow, Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch> on
the entire series.
-Daniel

> 
>  drivers/gpu/drm/bochs/bochs.h                |  4 +-
>  include/drm/drm_fourcc.h                     |  2 +
>  drivers/gpu/drm/bochs/bochs_fbdev.c          | 18 ++++++--
>  drivers/gpu/drm/bochs/bochs_hw.c             | 64 ++++++++++++++++++++++------
>  drivers/gpu/drm/bochs/bochs_kms.c            | 40 ++++++++++++++++-
>  drivers/gpu/drm/drm_fourcc.c                 | 28 ++++++++++++
>  drivers/gpu/drm/drm_framebuffer.c            | 15 ++-----
>  drivers/gpu/drm/drm_gem_framebuffer_helper.c |  6 ++-
>  drivers/gpu/drm/virtio/virtgpu_display.c     |  5 +++
>  drivers/gpu/drm/virtio/virtgpu_fb.c          |  2 +-
>  drivers/gpu/drm/virtio/virtgpu_gem.c         |  7 ++-
>  drivers/gpu/drm/virtio/virtgpu_plane.c       | 54 +----------------------
>  12 files changed, 155 insertions(+), 90 deletions(-)
> 
> -- 
> 2.9.3
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2018-09-21  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 11:12 [PATCH v3 0/5] drm: more byteorder fixes Gerd Hoffmann
2018-09-19 11:12 ` [PATCH v3 1/5] drm: move native byte order quirk to new drm_mode_legacy_fb_format2 function Gerd Hoffmann
2018-09-21  9:39   ` Daniel Vetter
2018-09-19 11:12 ` [PATCH v3 2/5] drm: use drm_mode_legacy_fb_format2 in drm_gem_fbdev_fb_create Gerd Hoffmann
2018-09-19 11:12 ` [PATCH v3 3/5] drm/bochs: fix DRM_FORMAT_* handling for big endian machines Gerd Hoffmann
2018-09-19 11:12 ` [PATCH v3 4/5] drm/bochs: support changing byteorder at mode set time Gerd Hoffmann
2018-09-19 11:12 ` [PATCH v3 5/5] drm/virtio: fix DRM_FORMAT_* handling Gerd Hoffmann
2018-09-21  9:40 ` Daniel Vetter [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=20180921094048.GF11082@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kraxel@redhat.com \
    --cc=michel@daenzer.net \
    /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