From: Sam Ravnborg <sam@ravnborg.org>
To: dri-devel@lists.freedesktop.org,
Alexey Brodkin <abrodkin@synopsys.com>,
Andrzej Hajda <a.hajda@samsung.com>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Chen Feng <puck.chen@hisilicon.com>,
David Airlie <airlied@linux.ie>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Philippe Cornu <philippe.cornu@st.com>,
Rongrong Zou <zourongrong@gmail.com>, Sean Paul <sean@poorly.run>,
Vincent Abriou <vincent.abriou@st.com>,
Xinliang Liu <z.liuxinliang@hisilicon.com>,
Xinwei Kong <kong.kongxinwei@hisilicon.com>,
Yannick Fertre <yannick.fertre@st.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 6/6] drm: remove drmP.h from drm_modeset_helper.h
Date: Thu, 24 Jan 2019 15:44:02 +0100 [thread overview]
Message-ID: <20190124144402.GA13670@ravnborg.org> (raw)
In-Reply-To: <20190124140320.GY3271@phenom.ffwll.local>
On Thu, Jan 24, 2019 at 03:03:20PM +0100, Daniel Vetter wrote:
> On Sat, Jan 19, 2019 at 09:40:14AM +0100, Sam Ravnborg wrote:
> > With the removal of drmP.h from drm_modeset_helper.h
> > the drmP.h are no longer included by any include files
> > in include/drm.
> > The drmP.h file is thus only included explicit
> > either in .c files or in local .h files.
> > This makes the process of deleting the drmP.h includes easier
> > as we have a more local dependency chain.
> >
> > Include build failure fixes in drm files after the drmP.h removal.
> >
> > Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > Cc: Maxime Ripard <maxime.ripard@bootlin.com>
> > Cc: Sean Paul <sean@poorly.run>
> > Cc: David Airlie <airlied@linux.ie>
> > Cc: Daniel Vetter <daniel@ffwll.ch>
>
> Merge the previous 5 patches from this series, but this now goes boom on
> vbox in staging. Needs another prep patch I think.
I did not check staging - sorry.
Will fix, most likely in the weekend.
Sam
next prev parent reply other threads:[~2019-01-24 14:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 8:40 [PATCH v5 0/6] drm: minimize drmP.h dependencies Sam Ravnborg
2019-01-19 8:40 ` Sam Ravnborg
2019-01-19 8:40 ` [PATCH v5 1/6] drm/stm: prepare for drmP.h removal from drm_modeset_helper.h Sam Ravnborg
2019-01-19 8:40 ` Sam Ravnborg
2019-01-19 8:40 ` [PATCH v5 2/6] drm/hisilicon/kirin: " Sam Ravnborg
2019-01-19 8:40 ` Sam Ravnborg
2019-01-19 8:40 ` [PATCH v5 3/6] drm/arcpgu: " Sam Ravnborg
2019-01-19 8:40 ` Sam Ravnborg
2019-01-19 8:40 ` [PATCH v5 4/6] drm/bridge: cdns: " Sam Ravnborg
2019-01-19 8:40 ` Sam Ravnborg
2019-01-19 8:40 ` [PATCH v5 5/6] drmi/rcar-du: " Sam Ravnborg
2019-01-19 8:40 ` Sam Ravnborg
2019-01-19 8:40 ` [PATCH v5 6/6] drm: remove drmP.h " Sam Ravnborg
2019-01-19 8:40 ` Sam Ravnborg
2019-01-24 14:03 ` Daniel Vetter
2019-01-24 14:03 ` Daniel Vetter
2019-01-24 14:44 ` Sam Ravnborg [this message]
2019-01-24 20:07 ` Sean Paul
2019-01-24 20:07 ` Sean Paul
2019-01-24 20:17 ` Sam Ravnborg
2019-01-24 20:17 ` Sam Ravnborg
2019-01-24 20:28 ` Sean Paul
2019-01-24 20:28 ` Sean Paul
2019-01-24 21:52 ` 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=20190124144402.GA13670@ravnborg.org \
--to=sam@ravnborg.org \
--cc=a.hajda@samsung.com \
--cc=abrodkin@synopsys.com \
--cc=airlied@linux.ie \
--cc=benjamin.gaignard@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=kong.kongxinwei@hisilicon.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=philippe.cornu@st.com \
--cc=puck.chen@hisilicon.com \
--cc=sean@poorly.run \
--cc=vincent.abriou@st.com \
--cc=yannick.fertre@st.com \
--cc=z.liuxinliang@hisilicon.com \
--cc=zourongrong@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.