From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: socfpga: Make the DT mmc node consistent
Date: Wed, 19 Aug 2015 00:06:13 +0200 [thread overview]
Message-ID: <201508190006.13444.marex@denx.de> (raw)
In-Reply-To: <55D395D7.2070404@opensource.altera.com>
On Tuesday, August 18, 2015 at 10:30:15 PM, Dinh Nguyen wrote:
> On 8/10/15 6:02 PM, Marek Vasut wrote:
> > The socfpga_cyclone5.dtsi has an mmc0 node, socrates has mmc node.
> > This makes aliases not very usable, so make everything into mmc0.
> > Moreover, zap the useless mmc alias while at this.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > ---
> >
> > arch/arm/dts/socfpga.dtsi | 3 +--
> > arch/arm/dts/socfpga_cyclone5_socrates.dts | 2 +-
> > 2 files changed, 2 insertions(+), 3 deletions(-)
>
> Acked-by: Dinh Nguyen <dinguyen@opensource.altera.com>
Applied to u-boot-socfpga/master, thanks!
Best regards,
Marek Vasut
prev parent reply other threads:[~2015-08-18 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 23:02 [U-Boot] [PATCH] arm: socfpga: Make the DT mmc node consistent Marek Vasut
2015-08-18 20:30 ` Dinh Nguyen
2015-08-18 22:06 ` Marek Vasut [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=201508190006.13444.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox