From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: mx5: Fix IPU port node placement
Date: Fri, 13 Jun 2014 09:45:33 +0200 [thread overview]
Message-ID: <1402645533.3507.2.camel@paszta.hi.pengutronix.de> (raw)
In-Reply-To: <1402618960-9735-1-git-send-email-marex@denx.de>
Am Freitag, den 13.06.2014, 02:22 +0200 schrieb Marek Vasut:
> The "port" node was misplaced in the original patch, therefore making
> the LCD dysfunctional on this board. Fix this by moving the "port" DT
> node into the "display {}" node.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Shawn Guo <shawn.guo@linaro.org>
> Cc: Philipp Zabel <p.zabel@pengutronix.de>
Acked-by: Philipp Zabel <p.zabel@pengutronix.de>
thanks
Philipp
next prev parent reply other threads:[~2014-06-13 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 0:22 [PATCH 1/2] ARM: dts: mx5: Fix IPU port node placement Marek Vasut
2014-06-13 0:22 ` [PATCH 2/2] ARM: dts: mx5: Move the display out of soc {} node Marek Vasut
2014-06-13 7:45 ` Philipp Zabel [this message]
2014-06-21 4:40 ` [PATCH 1/2] ARM: dts: mx5: Fix IPU port node placement Shawn Guo
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=1402645533.3507.2.camel@paszta.hi.pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).