From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bin Gao <bin.gao@linux.intel.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] serial_core: add pci uart early console support
Date: Sun, 24 May 2015 12:52:25 -0700 [thread overview]
Message-ID: <20150524195225.GA20120@kroah.com> (raw)
In-Reply-To: <20150522160659.GA108447@worksta>
On Fri, May 22, 2015 at 09:06:59AM -0700, Bin Gao wrote:
> On some Intel Atom SoCs, the legacy IO port UART(0x3F8) is not available.
> Instead, a 8250 compatible PCI uart can be used as early console.
> This patch adds pci support to the 8250 early console driver uart8250.
> For example, to enable pci uart(00:21.3) as early console on these
> platforms, append the following line to the kernel command line
> (assume baud rate is 115200):
> earlyprintk=uart8250,pci32,0:24.2,115200n8
>
> Signed-off-by: Bin Gao <bin.gao@intel.com>
> ---
> Changes in v4:
> - moved PCI_EARLY definition from arch/x86/Kconfig to drivers/pci/Kconfig
> - added 'earlyprintk' for x86 as alias to the early param 'earlycon'
What about the changes in earlier versions?
And why do I have 3 copies of different "v4" patches in my inbox?
Please resend this, as v5, correctly, and we can review it that way.
greg k-h
next prev parent reply other threads:[~2015-05-24 19:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 16:06 Bin Gao
2015-05-24 19:52 ` Greg Kroah-Hartman [this message]
2015-05-27 23:18 ` Bin Gao
2015-05-26 17:12 ` Peter Hurley
2015-05-27 23:14 ` Bin Gao
2015-05-28 0:21 ` Peter Hurley
2015-05-28 17:54 ` Bin Gao
-- strict thread matches above, loose matches on Subject: below --
2015-05-21 17:57 Bin Gao
2015-05-20 21:17 Bin Gao
2015-05-21 4:31 ` Greg Kroah-Hartman
2015-05-21 18:00 ` Bin Gao
2015-05-22 5:11 ` Greg Kroah-Hartman
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=20150524195225.GA20120@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bin.gao@linux.intel.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome