From: Shawn Guo <shawnguo@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: devicetree@vger.kernel.org, robh+dt@kernel.org,
linux-imx@nxp.com, kernel@pengutronix.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] ARM: dts: imx51-babbage: Fix the DVI output description
Date: Mon, 23 Dec 2019 15:01:45 +0800 [thread overview]
Message-ID: <20191223070144.GQ11523@dragon> (raw)
In-Reply-To: <20191213135838.28697-1-festevam@gmail.com>
On Fri, Dec 13, 2019 at 10:58:37AM -0300, Fabio Estevam wrote:
> imx51-babbage has a TFP410 chip that receives 24-bit RGB parallel
> input and convert it to DVI.
>
> Fix the device tree description to reflect the real hardware.
>
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
Applied both, thanks.
prev parent reply other threads:[~2019-12-23 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 13:58 [PATCH v2 1/2] ARM: dts: imx51-babbage: Fix the DVI output description Fabio Estevam
2019-12-13 13:58 ` [PATCH v2 2/2] ARM: imx_v6_v7_defconfig: Select the TFP410 driver Fabio Estevam
2019-12-23 7:01 ` Shawn Guo [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=20191223070144.GQ11523@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).