From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tbs2910: Fix error handling in board_mmc_init()
Date: Fri, 21 Nov 2014 16:43:01 +0100 [thread overview]
Message-ID: <546F5D85.7050303@denx.de> (raw)
In-Reply-To: <1416485012-3351-1-git-send-email-smoch@web.de>
On 20/11/2014 13:03, Soeren Moch wrote:
> When an invalid USDHC port is passed we should return -EINVAL instead of 0.
> Also, return the error immediately on fsl_esdhc_initialize() failure.
>
> Based on similar patches by Fabio Estevam for mx6sabresd, mx53loco, wandboard
>
> Signed-off-by: Soeren Moch <smoch@web.de>
> --
Applied to u-boot-imx, thanks !
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
prev parent reply other threads:[~2014-11-21 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 12:03 [U-Boot] [PATCH] tbs2910: Fix error handling in board_mmc_init() Soeren Moch
2014-11-20 15:36 ` Stefano Babic
2014-11-21 15:43 ` Stefano Babic [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=546F5D85.7050303@denx.de \
--to=sbabic@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