From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yinghai Lu <yinghai@kernel.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Warnings from silentoldconfig (Re: [GIT PULL] PCI updates for v3.11)
Date: Mon, 5 Aug 2013 10:39:43 +0200 [thread overview]
Message-ID: <20130805083943.GA14782@sepie.suse.cz> (raw)
In-Reply-To: <CA+55aFzSG8ny=79_MFik5xP99c7eb-LMKh0JzTKpbiEB8Wt=5Q@mail.gmail.com>
On Fri, Aug 02, 2013 at 01:28:25PM -0700, Linus Torvalds wrote:
> On Fri, Aug 2, 2013 at 11:17 AM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> >
> > Yinghai is still working on another SR-IOV-related fix or two, which
> > will be simpler if pciehp is non-modular, so I included the Kconfig
> > changes now to get them in earlier.
>
> Hmm. Doing a trivial "make allmoconfig" for testing, I get
>
> include/config/auto.conf:3014:warning: symbol value 'm' invalid for
> HOTPLUG_PCI_PCIE
> include/config/auto.conf:4711:warning: symbol value 'm' invalid for
> HOTPLUG_PCI
>
> but that may be a build system issue with stale data from the
> *previous* "make allmodconfig". Regardless, that makes me worried.
>
> Adding Michal Marek to the discussion. I'm currently doing a new "make
> allmodconfig" after having done a "git clean -dqfx" to see if the
> error remains. If it does, I will unpull. If it is gone, I'm going to
> assume the Kconfig changes are ok, but that our build system is
> missing some dependency.
Added Yann and the linux-kbuild list to CC. Reproducer:
git checkout 1fe0135
make mrproper
make allmodconfig
make silentoldconfig
git checkout aa8032b
make allmodconfig
make silentoldconfig
conf_write_autoconf() first calls conf_split_config() to generate the
include/config/**.h hierarchy, then generates include/config/auto.conf.
For some reason, conf_split_config() reads include/config/auto.conf,
which may not exist yet or may be out of date. Yann, can anything break
if we simply do not read that file from conf_split_config(), like this?
diff --git a/scripts/kconfig/confdata.c b/scripts/kconfig/confdata.c
index c55c227..8c90835 100644
--- a/scripts/kconfig/confdata.c
+++ b/scripts/kconfig/confdata.c
@@ -829,16 +829,12 @@ next:
static int conf_split_config(void)
{
- const char *name;
char path[PATH_MAX+1];
char *s, *d, c;
struct symbol *sym;
struct stat sb;
int res, i, fd;
- name = conf_get_autoconfig_name();
- conf_read_simple(name, S_DEF_AUTO);
-
if (chdir("include/config"))
return 1;
Thanks,
Michal
next prev parent reply other threads:[~2013-08-05 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 18:17 [GIT PULL] PCI updates for v3.11 Bjorn Helgaas
2013-08-02 20:28 ` Linus Torvalds
2013-08-02 21:24 ` Linus Torvalds
2013-08-05 8:39 ` Michal Marek [this message]
2013-08-05 9:26 ` Warnings from silentoldconfig (Re: [GIT PULL] PCI updates for v3.11) Yann E. MORIN
2013-08-05 22:58 ` Yann E. MORIN
2013-08-06 8:20 ` Michal Marek
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=20130805083943.GA14782@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=torvalds@linux-foundation.org \
--cc=yann.morin.1998@free.fr \
--cc=yinghai@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;
as well as URLs for NNTP newsgroup(s).