dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
	dri-devel@lists.freedesktop.org,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH 0/2] drm: fix fallout from drm_print.h include cleanups
Date: Mon, 03 Nov 2025 16:04:36 +0200	[thread overview]
Message-ID: <6fa3e821fdab9ecc83c1ef1241be71c3e10cf37e@intel.com> (raw)
In-Reply-To: <f2df4aa4-6c80-4f76-9539-47800b5166d9@suse.de>

On Mon, 03 Nov 2025, Thomas Zimmermann <tzimmermann@suse.de> wrote:
> Am 03.11.25 um 10:22 schrieb Jani Nikula:
>> Fix some (I guess inevitable) fallout from the drm_print.h cleanups.
>>
>> Note: I'm setting Fixes: f6e8dc9edf96 ("drm: include drm_print.h where
>> needed") instead of the ones removing drm_print.h includes, because that
>> was the one that was supposed to have them all.
>>
>> Jani Nikula (2):
>>    drm/renesas: include drm_print.h where needed
>>    drm/rockchip: include drm_print.h where needed
>
> Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
>
> for the series.

Thanks, pushed to drm-misc-next.

BR,
Jani.

>
>>
>>   drivers/gpu/drm/renesas/rz-du/rzg2l_du_drv.c | 1 +
>>   drivers/gpu/drm/rockchip/rockchip_drm_vop2.c | 1 +
>>   2 files changed, 2 insertions(+)
>>

-- 
Jani Nikula, Intel

      reply	other threads:[~2025-11-03 14:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03  9:22 [PATCH 0/2] drm: fix fallout from drm_print.h include cleanups Jani Nikula
2025-11-03  9:22 ` [PATCH 1/2] drm/renesas: include drm_print.h where needed Jani Nikula
2025-11-03  9:22 ` [PATCH 2/2] drm/rockchip: " Jani Nikula
2025-11-03  9:29 ` [PATCH 0/2] drm: fix fallout from drm_print.h include cleanups Thomas Zimmermann
2025-11-03 14:04   ` Jani Nikula [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=6fa3e821fdab9ecc83c1ef1241be71c3e10cf37e@intel.com \
    --to=jani.nikula@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tzimmermann@suse.de \
    /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