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: Wed, 14 Aug 2019 18:36:57 +0200 [thread overview]
Message-ID: <20190814163657.GA26556@ravnborg.org> (raw)
In-Reply-To: <20190812203805.GA10640@ravnborg.org>
> > 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.
Thierry reviewed all patches - thanks!
Applied to drm-misc-next and pushed out.
Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-08-14 16:36 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 ` [PATCH v2 0/4] drm: drop drmP in tda998x, tegra, arm, armada Sam Ravnborg
2019-08-14 16:36 ` Sam Ravnborg [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=20190814163657.GA26556@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).