Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	airlied@linux.ie, daniel@ffwll.ch,
	joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
	bskeggs@redhat.com
Cc: nouveau@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	Thomas Zimmermann <tzimmermann@suse.de>,
	dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/3] drm: Remove some includes of drm_legacy.h
Date: Mon, 17 May 2021 14:08:51 +0300	[thread overview]
Message-ID: <87lf8dhb24.fsf@intel.com> (raw)
In-Reply-To: <20210516185937.5644-1-tzimmermann@suse.de>

On Sun, 16 May 2021, Thomas Zimmermann <tzimmermann@suse.de> wrote:
> Remove include statements for DRM legacy headers. None of these
> dependencies is required. Built-tested w/o CONFIG_DRM_LEGACY set.
>
> These patches should probably go through drm-misc, like the rest
> of the legacy cleanups.

Acked-by: Jani Nikula <jani.nikula@intel.com>


>
> Thomas Zimmermann (3):
>   drm/i915: Don't include drm_legacy.h
>   drm/nouveau: Don't include drm_legacy.h
>   drm: Don't include drm_legacy.h in drm_lease.c
>
>  drivers/gpu/drm/drm_lease.c              | 1 -
>  drivers/gpu/drm/i915/gem/i915_gem_phys.c | 1 -
>  drivers/gpu/drm/i915/i915_drv.h          | 1 -
>  drivers/gpu/drm/nouveau/nouveau_ttm.c    | 2 --
>  4 files changed, 5 deletions(-)
>
>
> base-commit: 77fc6f68ed347b0a4c6969f6adac70026d5b1449
> prerequisite-patch-id: c2b2f08f0eccc9f5df0c0da49fa1d36267deb11d
> prerequisite-patch-id: c67e5d886a47b7d0266d81100837557fda34cb24
> prerequisite-patch-id: c59ca2ddb182af06006fa360ad3e90fe16b93d3a
> prerequisite-patch-id: 8c45deec68d6ab65d66f551b51b12acf2e9ae0b4
> prerequisite-patch-id: 742f08083f0d5776068a761b1e2432e8edc2bdf8
> prerequisite-patch-id: 39cfaf5f337ec53d3237bf2a700e77c84f789039
> --
> 2.31.1
>

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2021-05-17 11:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16 18:59 [Intel-gfx] [PATCH 0/3] drm: Remove some includes of drm_legacy.h Thomas Zimmermann
2021-05-16 18:59 ` [Intel-gfx] [PATCH 1/3] drm/i915: Don't include drm_legacy.h Thomas Zimmermann
2021-05-16 18:59 ` [Intel-gfx] [PATCH 2/3] drm/nouveau: " Thomas Zimmermann
2021-05-16 18:59 ` [Intel-gfx] [PATCH 3/3] drm: Don't include drm_legacy.h in drm_lease.c Thomas Zimmermann
2021-05-17 11:08 ` Jani Nikula [this message]
2021-05-17 11:56 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm: Remove some includes of drm_legacy.h Patchwork
2021-05-17 12:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-05-17 19:26 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork

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=87lf8dhb24.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@linux.ie \
    --cc=bskeggs@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --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