From: Philipp Zabel <p.zabel@pengutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Lucas Stach" <l.stach@pengutronix.de>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
dri-devel@lists.freedesktop.org, patchwork-lst@pengutronix.de
Subject: Re: [PATCH] drm/imx: move IPUv3 driver into separate subdirectory
Date: Fri, 16 Dec 2022 18:21:35 +0100 [thread overview]
Message-ID: <726d6dade0104b1dec7b9b8f7674a4bb137e8c3b.camel@pengutronix.de> (raw)
In-Reply-To: <20221216120352.7ke5msphsqfybagb@pengutronix.de>
On Fr, 2022-12-16 at 13:03 +0100, Uwe Kleine-König wrote:
> On Fri, Nov 25, 2022 at 12:25:19PM +0100, Lucas Stach wrote:
> > diff --git a/drivers/gpu/drm/imx/Makefile b/drivers/gpu/drm/imx/Makefile
> > index b644deffe948..909622864716 100644
> > --- a/drivers/gpu/drm/imx/Makefile
> > +++ b/drivers/gpu/drm/imx/Makefile
> > @@ -1,12 +1,4 @@
> > [...]
> > obj-$(CONFIG_DRM_IMX_DCSS) += dcss/
> > +obj-$(CONFIG_DRM_IMX) += ipuv3/
>
> I wonder if it would make sense to rename DRM_IMX to DRM_IMX_IPUV3 ?!
>
> > diff --git a/drivers/gpu/drm/imx/ipuv3/Kconfig b/drivers/gpu/drm/imx/ipuv3/Kconfig
> > new file mode 100644
> > index 000000000000..f518eb47a18e
> > --- /dev/null
> > +++ b/drivers/gpu/drm/imx/ipuv3/Kconfig
> > [...]
> > +config DRM_IMX_HDMI
> > + tristate "Freescale i.MX DRM HDMI"
> > + select DRM_DW_HDMI
> > + depends on DRM_IMX && OF
> > + help
> > + Choose this if you want to use HDMI on i.MX6.
> > +
>
> Trailing empty line could be dropped.
I'll do that when applying.
regards
Philipp
next prev parent reply other threads:[~2022-12-16 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 11:25 [PATCH] drm/imx: move IPUv3 driver into separate subdirectory Lucas Stach
2022-12-16 12:03 ` Uwe Kleine-König
2022-12-16 12:59 ` Lucas Stach
2022-12-16 17:21 ` Philipp Zabel [this message]
2022-12-16 17:20 ` Philipp Zabel
2022-12-16 18:06 ` Philipp Zabel
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=726d6dade0104b1dec7b9b8f7674a4bb137e8c3b.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=patchwork-lst@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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.