From: Fabio Estevam <fabio.estevam@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx25: Make the UART port number explicit in its setup function
Date: Wed, 2 Mar 2011 12:19:57 -0300 [thread overview]
Message-ID: <4D6E601D.9060709@freescale.com> (raw)
In-Reply-To: <4D6E0AB7.3050205@denx.de>
On 3/2/2011 6:15 AM, Stefano Babic wrote:
...
> As I do not see any fix for the current release, I have not yet merged
> it into u-boot-imx and I will do it when the window is open again. I
> imagine your patch is an introduction for further patches, where more as
> one uart is used, right ? Should it belong maybe to the same patchset ?
I was working on adding MX25PDK support and I think that that the UART reference should be explicit, as different boards can boot from different UART ports.
> checkpatch reports your patch is corrupted. Strange, I do not why, I
> have fixed myself.
Thanks, I haven?t noticed this.
Regards,
Fabio Estevam
next prev parent reply other threads:[~2011-03-02 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 19:50 [U-Boot] [PATCH] mx25: Make the UART port number explicit in its setup function Fabio Estevam
2011-03-02 1:31 ` Estevam Fabio-R49496
2011-03-02 9:15 ` Stefano Babic
2011-03-02 15:19 ` Fabio Estevam [this message]
2011-03-02 19:08 ` Stefano Babic
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=4D6E601D.9060709@freescale.com \
--to=fabio.estevam@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.