From: Sam Ravnborg <sam@ravnborg.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Martyn Welch <martyn.welch@collabora.co.uk>,
David Airlie <airlied@linux.ie>,
Peter Senna Tschudin <peter.senna@gmail.com>,
dri-devel@lists.freedesktop.org,
Martin Donnelly <martin.donnelly@ge.com>
Subject: Re: [PATCH v1 1/1] drm/bridge: drop drmP.h usage
Date: Sun, 19 May 2019 17:25:13 +0200 [thread overview]
Message-ID: <20190519152513.GA12957@ravnborg.org> (raw)
In-Reply-To: <20190519150754.GC5213@pendragon.ideasonboard.com>
Hi Laurent
Thanks for the quick feedback.
> > @@ -15,14 +15,17 @@
> > #include <linux/of_device.h>
> > #include <linux/pm_runtime.h>
> > #include <linux/reset.h>
> > -#include <drm/drmP.h>
> > +
> > #include <drm/drm_atomic_helper.h>
> > #include <drm/drm_bridge.h>
> > #include <drm/drm_crtc.h>
> > #include <drm/drm_mipi_dsi.h>
> > #include <drm/drm_of.h>
> > +#include <drm/drm_print.h>
> > #include <drm/drm_probe_helper.h>
> > +
> > #include <drm/bridge/dw_mipi_dsi.h>
>
> If you separate this file fromt he rest of the drm/ includes, you should
> do the same in drivers/gpu/drm/bridge/synopsys/dw-hdmi.c for
> consistency. I'm fine either way.
>
> > index a20e454ddd64..170f162ffa55 100644
> > --- a/drivers/gpu/drm/bridge/tc358764.c
> > +++ b/drivers/gpu/drm/bridge/tc358764.c
> > @@ -7,18 +7,22 @@
> > * Maciej Purski <m.purski@samsung.com>
> > */
> >
> > +#include <linux/delay.h>
> > +#include <linux/gpio/consumer.h>
> > +#include <linux/module.h>
> > +#include <linux/of_graph.h>
> > +#include <linux/regulator/consumer.h>
> > +
> > +#include <video/mipi_display.h>
> > +
> > #include <drm/drm_atomic_helper.h>
> > #include <drm/drm_crtc.h>
> > #include <drm/drm_fb_helper.h>
> > #include <drm/drm_mipi_dsi.h>
> > #include <drm/drm_of.h>
> > #include <drm/drm_panel.h>
> > +#include <drm/drm_print.h>
> > #include <drm/drm_probe_helper.h>
> > -#include <drm/drmP.h>
> > -#include <linux/gpio/consumer.h>
> > -#include <linux/of_graph.h>
> > -#include <linux/regulator/consumer.h>
> > -#include <video/mipi_display.h>
>
> Similarly, in drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c you have
> video/ after drm/, while it's the other way around. I think we should
> pick one order and stick with it.
Well done to spot this inconsistency.
I will go through the files and consistently use following order:
<linux/*>
<asm/*>
<video/*>
<drm/*>
""
This seems to match the majority but all variants can be found.
And then the principle is:
- most general includes first, with linux/* first
- drm includes second-last
- local drm includes last
>
> With these small issues fixed,
>
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Thanks. I will post a v2 - where I can also fix so the mail is sent to
the relevant people (my cc: was missing some this time).
Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-05-19 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 11:00 [PATCH v1 1/1] drm/bridge: drop drmP.h usage Sam Ravnborg
2019-05-19 15:07 ` Laurent Pinchart
2019-05-19 15:25 ` 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=20190519152513.GA12957@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=martin.donnelly@ge.com \
--cc=martyn.welch@collabora.co.uk \
--cc=peter.senna@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