From: info@lategoodbye.de (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] arm: mxs: dts: small fixes for I2SE's duckbills
Date: Tue, 01 Apr 2014 19:28:33 +0200 [thread overview]
Message-ID: <533AF741.4080402@lategoodbye.de> (raw)
In-Reply-To: <1395960690-19531-1-git-send-email-mhei@heimpold.de>
Am 27.03.2014 23:51, schrieb Michael Heimpold:
> This series fixes two issues with the DT file: first, it frees up
> some GPIOs which are mis-used by MMC interface, and second, it
> fixes the GPIO used to reset the ethernet phy.
>
> While at it, use symbolic names for LED definitions.
>
> Changes in v2:
> - add missing patch for imx28.dtsi to include gpio.h
>
>
> Michael Heimpold (4):
> arm: mxs: dt: imx28-duckbill: fix mmc settings
> arm: mxs: dt: imx28-duckbill: fix phy reset gpio
> arm: mxs: dt: imx28: include gpio.h to allow use of symbolic names
> arm: mxs: dt: imx28-duckbill: use symbolic names from gpio.h
>
> arch/arm/boot/dts/imx28-duckbill.dts | 12 ++++++------
> arch/arm/boot/dts/imx28.dtsi | 1 +
> 2 files changed, 7 insertions(+), 6 deletions(-)
>
They all look good to me.
Acked-by: Stefan Wahren <stefan.wahren@i2se.com>
BR Stefan Wahren
next prev parent reply other threads:[~2014-04-01 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 22:51 [PATCH v2 0/4] arm: mxs: dts: small fixes for I2SE's duckbills Michael Heimpold
2014-03-27 22:51 ` [PATCH v2 1/4] arm: mxs: dt: imx28-duckbill: fix mmc settings Michael Heimpold
2014-03-27 22:51 ` [PATCH v2 2/4] arm: mxs: dt: imx28-duckbill: fix phy reset gpio Michael Heimpold
2014-03-27 22:51 ` [PATCH v2 3/4] arm: mxs: dt: imx28: include gpio.h to allow use of symbolic names Michael Heimpold
2014-03-27 22:51 ` [PATCH v2 4/4] arm: mxs: dt: imx28-duckbill: use symbolic names from gpio.h Michael Heimpold
2014-04-01 17:28 ` Stefan Wahren [this message]
2014-04-02 8:52 ` [PATCH v2 0/4] arm: mxs: dts: small fixes for I2SE's duckbills Shawn Guo
2014-04-02 9:00 ` 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=533AF741.4080402@lategoodbye.de \
--to=info@lategoodbye.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).