From: LW@KARO-electronics.de (Lothar Waßmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Enable UART3 on TX28
Date: Mon, 21 Mar 2011 16:52:54 +0100 [thread overview]
Message-ID: <19847.29782.578106.44656@ipc1.ka-ro> (raw)
In-Reply-To: <201103211627.12922.arnd@arndb.de>
Hi,
> On Monday 21 March 2011, Lothar Wa?mann wrote:
> > + /* UART3 */
> > + MX28_PAD_AUART3_RX__AUART3_RX,
> > + MX28_PAD_AUART3_TX__AUART3_TX,
> > + MX28_PAD_AUART3_RTS__AUART3_RTS,
> > + MX28_PAD_AUART3_CTS__AUART3_CTS,
> > +
>
> The patch is missing changelog, signed-off-by and diff header.
> Content-wise, it seems ok.
>
I know. Rogue git-send-email...
I already resent it.
Lothar Wa?mann
--
___________________________________________________________
Ka-Ro electronics GmbH | Pascalstra?e 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Gesch?ftsf?hrer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996
www.karo-electronics.de | info at karo-electronics.de
___________________________________________________________
prev parent reply other threads:[~2011-03-21 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 14:36 Enable UART3 on TX28 Lothar Waßmann
2011-03-21 15:27 ` Arnd Bergmann
2011-03-21 15:52 ` Lothar Waßmann [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=19847.29782.578106.44656@ipc1.ka-ro \
--to=lw@karo-electronics.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