From: alan@linux.intel.com (Alan Cox)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] serial: pl011: honour serial aliases in device tree
Date: Tue, 4 Sep 2012 12:42:38 +0100 [thread overview]
Message-ID: <20120904124238.79635a2d@bob.linux.org.uk> (raw)
In-Reply-To: <000001cd8a8d$54bbad60$fe330820$@leach@arm.com>
On Tue, 4 Sep 2012 12:06:27 +0100
"Matthew Leach" <matthew.leach@arm.com> wrote:
> Alan,
>
> > If the order of UART nodes is changed in the device tree, then tty
> > dev devices are attached to different serial ports causing the
> > console to be directed to a different physical serial port. The
> > "serial" aliases in the device tree should prevent this.
>
> Are you okay merging this patch?
Yes
next prev parent reply other threads:[~2012-09-04 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 15:41 [PATCH v3] serial: pl011: honour serial aliases in device tree Matthew Leach
2012-09-04 11:06 ` Matthew Leach
2012-09-04 11:42 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-22 16:25 Matthew Leach
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=20120904124238.79635a2d@bob.linux.org.uk \
--to=alan@linux.intel.com \
--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).