AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org>
To: Alex Deucher <alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Alex Deucher <alexander.deucher-5C7GfCeVMHo@public.gmane.org>,
	daniel.vetter-/w4YWyX8dFk@public.gmane.org,
	airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: drop drmP.h usage? [Was: [pull] amdgpu, amdkfd drm-next-5.3]
Date: Thu, 30 May 2019 08:30:29 +0200	[thread overview]
Message-ID: <20190530063029.GA20000@ravnborg.org> (raw)
In-Reply-To: <20190529220944.14464-1-alexander.deucher-5C7GfCeVMHo@public.gmane.org>

Hi Alex et all.

> - Various cleanups

Any chance to persuade one of you guys to sweep through the amd / raedeon
tree and drop use of the deprecated header drmP.h?

Status at the moment (drm-misc-next):
$git grep drmP | cut -d '/' -f 1  | uniq -c | sort -n | tail -n 10
     11 meson
     12 mediatek
     13 vmwgfx
     15 rockchip
     16 sti
     18 sun4i
     24 exynos
     27 nouveau
    103 radeon
    110 amd

nouveau is already taken care of, the cleanup is in their tree.
amd and radeon are the two "worst" drivers in this respect at the
moment.

Thanks,
	Sam
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2019-05-30  6:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 22:09 [pull] amdgpu, amdkfd drm-next-5.3 Alex Deucher
     [not found] ` <20190529220944.14464-1-alexander.deucher-5C7GfCeVMHo@public.gmane.org>
2019-05-30  6:30   ` Sam Ravnborg [this message]
2019-06-03 15:35   ` Daniel Vetter
     [not found]     ` <CAKMK7uFFB7ME=d1U-SpCUEtVbysAuW2H--=4EeKKJYofeggLoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-06-04 14:46       ` Alex Deucher
     [not found]         ` <CADnq5_O42stLJBp71kknaoP=hPR828nbD5diC=HG-Wwag5--PA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-06-04 16:46           ` Daniel Vetter

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=20190530063029.GA20000@ravnborg.org \
    --to=sam-uyr5n9q2vtjg9huczpvpmw@public.gmane.org \
    --cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=alexander.deucher-5C7GfCeVMHo@public.gmane.org \
    --cc=alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=daniel.vetter-/w4YWyX8dFk@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /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