From: Ralf Baechle <ralf@linux-mips.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Thierry Reding <thierry.reding@avionic-design.de>,
Bjorn Helgaas <bhelgaas@google.com>,
David Daney <ddaney.cavm@gmail.com>,
linux-pci@vger.kernel.org, linux-mips <linux-mips@linux-mips.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: PCI Section mismatch error in linux-next.
Date: Tue, 21 Aug 2012 19:04:57 +0200 [thread overview]
Message-ID: <20120821170456.GA18994@linux-mips.org> (raw)
In-Reply-To: <CAMuHMdWfhATFQrP-ZiMi6Ub3ZbOgUhe7S_fVUzc7zOwDxRNsyw@mail.gmail.com>
On Tue, Aug 21, 2012 at 04:32:45PM +0200, Geert Uytterhoeven wrote:
> Anyone who disables CONFIG_HOTPLUG in his defconfig files?
>
> $ git grep CONFIG_HOTPLUG arch/*/*config
> arch/frv/defconfig:# CONFIG_HOTPLUG is not set
> arch/h8300/defconfig:# CONFIG_HOTPLUG is not set
> arch/um/defconfig:CONFIG_HOTPLUG=y
> $
>
> Yep, (at least --- not all defconfigs are up-to-date) frv and h8300.
Since we started stripping all the defconfigs down grepping through
arch/*/configs/ doesn't yield much useful information anymore :-(
There are currently 8 MIPS default configurations that dondo not enable
CONFIG_HOTPLUG. I didn't check other architectures.
Ralf
next prev parent reply other threads:[~2012-08-21 17:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 17:36 PCI Section mismatch error in linux-next David Daney
2012-08-17 17:44 ` Bjorn Helgaas
2012-08-17 18:29 ` Thierry Reding
2012-08-17 19:32 ` Bjorn Helgaas
2012-08-17 20:07 ` Thierry Reding
2012-08-17 20:39 ` Bjorn Helgaas
2012-08-17 20:48 ` Thierry Reding
2012-08-17 21:06 ` Bjorn Helgaas
2012-08-17 21:22 ` Thierry Reding
2012-08-17 21:07 ` Thierry Reding
2012-08-17 21:25 ` Bjorn Helgaas
2012-08-17 21:32 ` Thierry Reding
2012-08-17 21:46 ` Bjorn Helgaas
2012-08-20 5:30 ` Greg KH
2012-08-20 7:16 ` Thierry Reding
2012-08-21 14:32 ` Geert Uytterhoeven
2012-08-21 17:04 ` Ralf Baechle [this message]
2012-08-21 18:15 ` Geert Uytterhoeven
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=20120821170456.GA18994@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=bhelgaas@google.com \
--cc=ddaney.cavm@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-pci@vger.kernel.org \
--cc=thierry.reding@avionic-design.de \
/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).