From: Jani Nikula <jani.nikula@intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org,
maarten.lankhorst@linux.intel.com,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@redhat.com>,
simona.vetter@ffwll.ch
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v3 0/4] drm: replace drm_print.h includes from headers with a forward declaration
Date: Fri, 31 Oct 2025 12:01:47 +0200 [thread overview]
Message-ID: <18ad4c11261b85614f7e3a2aabe611f2ecbf16a5@intel.com> (raw)
In-Reply-To: <c4e3b172-3df8-4d1b-a1b0-51cacae56f0c@suse.de>
On Thu, 30 Oct 2025, Thomas Zimmermann <tzimmermann@suse.de> wrote:
> Am 30.10.25 um 10:31 schrieb Jani Nikula:
>> Considering that this touches a lot of drivers, albeit just the include
>> lists and thus highly unlikely to cause functional changes or hard
>> conflicts, can I go ahead and merge this to drm-misc-next?
>
> Of course, go ahead.
Done, thanks again!
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-10-31 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 10:39 [PATCH v3 0/4] drm: replace drm_print.h includes from headers with a forward declaration Jani Nikula
2025-10-29 10:39 ` [PATCH v3 1/4] drm: include drm_print.h where needed Jani Nikula
2025-10-29 10:39 ` [PATCH v3 2/4] drm/buddy: replace drm_print.h include with a forward declaration Jani Nikula
2025-10-29 10:39 ` [PATCH v3 3/4] drm/mm: " Jani Nikula
2025-10-29 10:39 ` [PATCH v3 4/4] drm/ttm: " Jani Nikula
[not found] ` <41bb4163-8f5b-47c5-8121-7010147bc5e6@suse.de>
2025-10-30 9:31 ` [PATCH v3 0/4] drm: replace drm_print.h includes from headers " Jani Nikula
2025-10-30 11:17 ` Thomas Zimmermann
2025-10-31 10:01 ` 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=18ad4c11261b85614f7e3a2aabe611f2ecbf16a5@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona.vetter@ffwll.ch \
--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;
as well as URLs for NNTP newsgroup(s).