All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 0/7] drm: Review of mode copies
Date: Tue, 8 Nov 2022 16:53:59 +0100	[thread overview]
Message-ID: <Y2p7l/6hy8NxO2rP@phenom.ffwll.local> (raw)
In-Reply-To: <20221107192545.9896-1-ville.syrjala@linux.intel.com>

On Mon, Nov 07, 2022 at 09:25:38PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> Repost of the stragglers from
> https://patchwork.freedesktop.org/series/100393/
> 
> Note that I didn't rerun the cocci stuff, nor have I had
> time to come up with something to inluce the cocci scripts
> in the tree. So it's possible this is missing some new
> things that have snuck in the meantime.
> 
> Ville Syrjälä (7):
>   drm/amdgpu: Use drm_mode_init() for on-stack modes
>   drm/hisilicon: Use drm_mode_init() for on-stack modes
>   drm/msm: Use drm_mode_init() for on-stack modes
>   drm/msm: Use drm_mode_copy()
>   drm/mtk: Use drm_mode_init() for on-stack modes
>   drm/rockchip: Use drm_mode_copy()
>   drm/sti: Use drm_mode_copy()

On the series:

Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>

Imo ping Alex/Rob and stuff everything left into drm-misc-next.
-Daniel

> 
>  drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c    | 3 ++-
>  drivers/gpu/drm/hisilicon/kirin/dw_drm_dsi.c         | 2 +-
>  drivers/gpu/drm/mediatek/mtk_hdmi.c                  | 2 +-
>  drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys_vid.c | 7 +++++--
>  drivers/gpu/drm/msm/dp/dp_display.c                  | 2 +-
>  drivers/gpu/drm/rockchip/cdn-dp-core.c               | 2 +-
>  drivers/gpu/drm/rockchip/inno_hdmi.c                 | 2 +-
>  drivers/gpu/drm/rockchip/rk3066_hdmi.c               | 2 +-
>  drivers/gpu/drm/sti/sti_dvo.c                        | 2 +-
>  drivers/gpu/drm/sti/sti_hda.c                        | 2 +-
>  drivers/gpu/drm/sti/sti_hdmi.c                       | 2 +-
>  11 files changed, 16 insertions(+), 12 deletions(-)
> 
> -- 
> 2.37.4
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  parent reply	other threads:[~2022-11-08 15:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 19:25 [PATCH v2 0/7] drm: Review of mode copies Ville Syrjala
2022-11-07 19:25 ` [PATCH v2 1/7] drm/amdgpu: Use drm_mode_init() for on-stack modes Ville Syrjala
2022-11-07 19:25   ` Ville Syrjala
2022-11-10 15:27   ` Alex Deucher
2022-11-10 15:27     ` Alex Deucher
2022-11-07 19:25 ` [PATCH v2 2/7] drm/hisilicon: " Ville Syrjala
2022-11-07 19:25 ` [PATCH v2 3/7] drm/msm: " Ville Syrjala
2022-11-07 19:25   ` Ville Syrjala
2022-11-07 19:25 ` [PATCH v2 4/7] drm/msm: Use drm_mode_copy() Ville Syrjala
2022-11-07 19:25   ` Ville Syrjala
2022-11-07 19:25 ` [PATCH v2 5/7] drm/mtk: Use drm_mode_init() for on-stack modes Ville Syrjala
2022-11-07 19:25 ` [PATCH v2 6/7] drm/rockchip: Use drm_mode_copy() Ville Syrjala
2022-11-07 19:25   ` Ville Syrjala
2022-11-07 19:25   ` Ville Syrjala
2022-11-07 19:25 ` [PATCH v2 7/7] drm/sti: " Ville Syrjala
2022-11-08 15:53 ` Daniel Vetter [this message]
2022-11-08 22:13   ` [PATCH v2 0/7] drm: Review of mode copies Alex Deucher
2022-11-09 11:17     ` Ville Syrjälä

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=Y2p7l/6hy8NxO2rP@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.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.