From: Paul Bolle <pebolle@tiscali.nl>
To: Bin Gao <bin.gao@linux.intel.com>
Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Hurley <peter@hurleysoftware.com>,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: [PATCH v3 1/2] serial_core: add pci uart early console support
Date: Tue, 19 May 2015 14:01:07 +0200 [thread overview]
Message-ID: <1432036867.9091.75.camel@x220> (raw)
In-Reply-To: <20150518212152.GA95407@worksta>
On Mon, 2015-05-18 at 14:21 -0700, Bin Gao wrote:
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -2228,6 +2228,8 @@ config PCI
> your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
> VESA. If you have PCI, say Y, otherwise N.
>
> + select HAVE_EARLY_PCI
> +
It's legal to have options after the help text of a Kconfig entry. It's
also very uncommon to do that. Please put this select statement before
the line reading "---help---" of the PCI entry.
> +config HAVE_EARLY_PCI
> + def_bool y
You probably want just
bool
here. Because this symbol has no further dependencies, which means
HAVE_EARLY_PCI will now always be set to 'y'. That, in turn, makes the
select you added above pointless.
> + help
> + This option indicates that a group of APIs are available (in
> + asm/pci-direct.h) so the kernel can access pci config registers
> + before the PCI subsystem is initialized. Any arch that supports
Is this expected to be used outside of X86?
> + early pci APIs must enable this option which is required by arch
> + independent codes, e.g. uart8250 pci early console driver.
> +
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-05-19 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 21:21 [PATCH v3 1/2] serial_core: add pci uart early console support Bin Gao
2015-05-19 12:01 ` Paul Bolle [this message]
2015-05-19 17:32 ` Bin Gao
2015-05-20 9:16 ` Paul Bolle
2015-05-20 17:59 ` Bin Gao
2015-05-20 17:50 ` Paul Bolle
2015-05-20 21:11 ` Bin Gao
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=1432036867.9091.75.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=bin.gao@linux.intel.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter@hurleysoftware.com \
/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