linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: dri-devel@lists.freedesktop.org
Cc: David Airlie <airlied@linux.ie>,
	Liviu Dudau <liviu.dudau@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	malidp@foss.arm.com, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 0/4] drm: drop drmP in tda998x, tegra, arm, armada
Date: Mon, 12 Aug 2019 22:38:05 +0200	[thread overview]
Message-ID: <20190812203805.GA10640@ravnborg.org> (raw)
In-Reply-To: <20190804094132.29463-1-sam@ravnborg.org>

Hi all.

On Sun, Aug 04, 2019 at 11:41:28AM +0200, Sam Ravnborg wrote:
> This set of patches is one of the final steps before
> we have succeeded to stop using drmP.h in all of drm/.
> 
> There is a few patches in flight through other trees
> and the plan is that all users shall be gone in the
> upstream kernel after next merge window.
> 
> The patches has seen build test with various configs
> with various architectures.
> 
> The patches has been sent before, but to my best knowledge
> they have not been applied anywhere.
> All four patches are based on drm-misc-next,
> but I checked that the tda998x patch can be applied to
> the tda998x tree.
> 
> There are no dependencies between the patches.
> 
> v2:
> - rebase on top of drm-misc-next
> 
> To maintainers: (Assuming the patch are OK)
> Please let me know if you take the patch, or request
> me to apply it to drm-misc-next.
> Or let me me know if the patch should be based on another tree.

ping...

This patchset is one of the last steps to get rid of drmP.h.
Other patches are applied to various sub-system trees.

The idea is that after next merge window can drop drmP.h.
As long as we keep drmP.h around new users will sneak in.

	Sam

> 
> Sam Ravnborg (4):
>       drm/i2c/tda998x: drop use of drmP.h
>       drm/tegra: drop use of drmP.h
>       drm/armada: drop use of drmP.h
>       drm/arm: drop use of drmP.h
> 
>  drivers/gpu/drm/arm/hdlcd_crtc.c        | 12 +++++++-----
>  drivers/gpu/drm/arm/hdlcd_drv.c         |  7 ++++++-
>  drivers/gpu/drm/arm/malidp_crtc.c       | 11 +++++++----
>  drivers/gpu/drm/arm/malidp_drv.c        |  8 +++++---
>  drivers/gpu/drm/arm/malidp_drv.h        |  7 ++++---
>  drivers/gpu/drm/arm/malidp_hw.c         |  7 ++++++-
>  drivers/gpu/drm/arm/malidp_mw.c         |  5 +++--
>  drivers/gpu/drm/arm/malidp_planes.c     |  4 +++-
>  drivers/gpu/drm/armada/armada_crtc.c    | 10 +++++++---
>  drivers/gpu/drm/armada/armada_debugfs.c |  8 ++++++--
>  drivers/gpu/drm/armada/armada_drm.h     |  5 ++++-
>  drivers/gpu/drm/armada/armada_drv.c     |  8 ++++++++
>  drivers/gpu/drm/armada/armada_fb.c      |  3 +++
>  drivers/gpu/drm/armada/armada_fbdev.c   |  3 +++
>  drivers/gpu/drm/armada/armada_gem.c     |  7 ++++++-
>  drivers/gpu/drm/armada/armada_overlay.c |  8 +++++---
>  drivers/gpu/drm/armada/armada_plane.c   |  4 +++-
>  drivers/gpu/drm/armada/armada_trace.h   |  5 ++++-
>  drivers/gpu/drm/i2c/tda998x_drv.c       |  2 +-
>  drivers/gpu/drm/tegra/dc.c              | 13 +++++++++----
>  drivers/gpu/drm/tegra/dpaux.c           |  5 +++--
>  drivers/gpu/drm/tegra/drm.c             |  8 ++++++++
>  drivers/gpu/drm/tegra/drm.h             |  3 +--
>  drivers/gpu/drm/tegra/dsi.c             |  8 +++++---
>  drivers/gpu/drm/tegra/fb.c              |  6 ++++--
>  drivers/gpu/drm/tegra/gem.c             |  3 +++
>  drivers/gpu/drm/tegra/gem.h             |  1 -
>  drivers/gpu/drm/tegra/gr2d.c            |  1 +
>  drivers/gpu/drm/tegra/hdmi.c            |  5 +++++
>  drivers/gpu/drm/tegra/hub.c             |  3 ++-
>  drivers/gpu/drm/tegra/hub.h             |  1 -
>  drivers/gpu/drm/tegra/plane.c           |  1 +
>  drivers/gpu/drm/tegra/sor.c             |  3 +++
>  drivers/gpu/drm/tegra/vic.c             |  1 +
>  34 files changed, 137 insertions(+), 49 deletions(-)
> 
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-08-12 20:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-04  9:41 [PATCH v2 0/4] drm: drop drmP in tda998x, tegra, arm, armada Sam Ravnborg
2019-08-04  9:41 ` [PATCH v2 1/4] drm/i2c/tda998x: drop use of drmP.h Sam Ravnborg
2019-08-13  9:30   ` Thierry Reding
2019-08-04  9:41 ` [PATCH v2 2/4] drm/tegra: " Sam Ravnborg
2019-08-13  9:30   ` Thierry Reding
2019-08-04  9:41 ` [PATCH v2 3/4] drm/armada: " Sam Ravnborg
2019-08-13  9:31   ` Thierry Reding
2019-08-04  9:41 ` [PATCH v2 4/4] drm/arm: " Sam Ravnborg
2019-08-13  9:32   ` Thierry Reding
2019-08-12 20:38 ` Sam Ravnborg [this message]
2019-08-14 16:36   ` [PATCH v2 0/4] drm: drop drmP in tda998x, tegra, arm, armada Sam Ravnborg

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=20190812203805.GA10640@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=liviu.dudau@arm.com \
    --cc=malidp@foss.arm.com \
    --cc=thierry.reding@gmail.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 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).