From: Mason <slash.tmp@free.fr>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Sebastian Frias <sf84@laposte.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mans Rullgard <mans@mansr.com>
Subject: Re: [RFC PATCH] always probe UART HW when options are not specified
Date: Tue, 12 Jan 2016 23:26:19 +0100 [thread overview]
Message-ID: <56957D8B.3080906@free.fr> (raw)
In-Reply-To: <5695584E.3040902@hurleysoftware.com>
On 12/01/2016 20:47, Peter Hurley wrote:
> I expect that patch to go into -next sometime during the 4.5-rc cycle.
Do you mean the "Add Au1x00/RT288x earlycon support" patch?
I find it strange that you have rt288x_putc while also
using AU1x00_FOO. Seems like mixing naming styles.
Did you see my post about the underlying IP block?
Might be appropriate to use that name there?
Regards.
next prev parent reply other threads:[~2016-01-12 22:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5672D18E.8000301@laposte.net>
2015-12-17 15:23 ` Måns Rullgård
2015-12-17 16:29 ` Peter Hurley
2015-12-17 16:48 ` Sebastian Frias
2015-12-17 17:21 ` Greg Kroah-Hartman
2015-12-17 19:05 ` Sebastian Frias
2015-12-17 17:48 ` Peter Hurley
2015-12-17 18:21 ` Sebastian Frias
2015-12-17 20:09 ` Peter Hurley
2015-12-18 13:53 ` Sebastian Frias
2015-12-18 15:03 ` Peter Hurley
2015-12-21 16:50 ` Sebastian Frias
2015-12-22 17:56 ` Sebastian Frias
2016-01-11 15:07 ` Sebastian Frias
2016-01-11 16:11 ` Peter Hurley
2016-01-11 17:56 ` Sebastian Frias
2016-01-11 19:06 ` Peter Hurley
2016-01-11 19:57 ` Peter Hurley
2016-01-11 20:21 ` Peter Hurley
2016-01-12 9:37 ` Mason
2016-01-12 14:22 ` Sebastian Frias
2016-01-12 19:47 ` Peter Hurley
2016-01-12 22:26 ` Mason [this message]
2016-01-12 22:42 ` Peter Hurley
2016-01-13 11:14 ` Sebastian Frias
2016-01-13 16:34 ` Peter Hurley
2016-01-18 11:52 ` Sebastian Frias
2016-01-12 14:14 ` Sebastian Frias
2016-01-12 21:18 ` Peter Hurley
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=56957D8B.3080906@free.fr \
--to=slash.tmp@free.fr \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mans@mansr.com \
--cc=peter@hurleysoftware.com \
--cc=sf84@laposte.net \
/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
Powered by JetHome