From: Sam Ravnborg <sam@ravnborg.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: "Marek Vasut" <marex@denx.de>, "David Airlie" <airlied@linux.ie>,
"DRI mailing list" <dri-devel@lists.freedesktop.org>,
"Julien BOIBESSOT" <julien.boibessot@armadeus.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Sébastien Szymanski" <sebastien.szymanski@armadeus.com>,
"Shawn Guo" <shawnguo@kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/1] drm: mxsfb: add i.MX6UL in Kconfig
Date: Mon, 29 Jul 2019 16:37:49 +0200 [thread overview]
Message-ID: <20190729143749.GB16927@ravnborg.org> (raw)
In-Reply-To: <CAOMZO5CFqQEdqgwyHZ2E2F22QDgG8SUjBM0y4Y6qyn8Tqo4O0g@mail.gmail.com>
Hi Sébastien,
On Mon, Jul 29, 2019 at 11:27:37AM -0300, Fabio Estevam wrote:
> Hi Sébastien,
>
> On Mon, Jul 29, 2019 at 11:14 AM Sébastien Szymanski
> <sebastien.szymanski@armadeus.com> wrote:
>
> > config DRM_MXSFB
> > - tristate "i.MX23/i.MX28/i.MX6SX MXSFB LCD controller"
> > + tristate "i.MX23/i.MX28/i.MX6SX/i.MX6UL MXSFB LCD controller"
>
> This IP is also found on i.MX6SL, i.MX7D, i.MX7S, i.MX8M, i.MX8QXP, etc
>
> I think it would be better if we do not keep increasing the list of
> supported SoCs in the Kconfig text.
Could we throw a COMPILE_TEST in the mix so we get better build
coverage too?
Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-07-29 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 14:13 [PATCH 1/1] drm: mxsfb: add i.MX6UL in Kconfig Sébastien Szymanski
2019-07-29 14:27 ` Fabio Estevam
2019-07-29 14:37 ` Sam Ravnborg [this message]
2019-07-29 15:51 ` Fabio Estevam
2019-07-29 17:50 ` 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=20190729143749.GB16927@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=julien.boibessot@armadeus.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=marex@denx.de \
--cc=sebastien.szymanski@armadeus.com \
--cc=shawnguo@kernel.org \
/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