From: Paul Bolle <pebolle@tiscali.nl>
To: Jarod Wilson <jarod@redhat.com>
Cc: Tony Luck <tony.luck@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Prarit Bhargava <prarit@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Odd build breakage in 4.9-rc7
Date: Wed, 30 Nov 2016 22:42:07 +0100 [thread overview]
Message-ID: <1480542127.27962.17.camel@tiscali.nl> (raw)
In-Reply-To: <222b47f2-55e0-3410-c87d-183ca5e2a0fe@redhat.com>
On Wed, 2016-11-30 at 16:35 -0500, Jarod Wilson wrote:
> Just to confirm, with CONFIG_TRIM_UNUSED_KSYMS unset, the build behaves
> normally, no ERROR spew.
And if MODVERSIONS is not set?
My current theory is that setting MODVERSIONS, somehow, hides the ERROR spew.
Because that could explain your bisect. Linus' commit turns of MODVERSIONS the
hard way. And, naturally, this theory fails if your .configs never had
MODVERSIONS set in the first place.
I'm testing all this right now, but you probably command more powerful
machines and could beat me in testing this theory.
Thanks,
Paul Bolle
next prev parent reply other threads:[~2016-11-30 21:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 17:24 Jarod Wilson
2016-11-30 18:18 ` Linus Torvalds
2016-11-30 18:28 ` Prarit Bhargava
2016-11-30 18:36 ` Linus Torvalds
2016-11-30 18:50 ` Prarit Bhargava
2016-11-30 19:00 ` Jarod Wilson
2016-11-30 19:35 ` Linus Torvalds
2016-11-30 22:41 ` Nicolas Pitre
2016-12-01 12:47 ` Prarit Bhargava
2016-12-01 14:03 ` Prarit Bhargava
2016-12-01 15:22 ` Jarod Wilson
2016-11-30 22:54 ` Nicolas Pitre
2016-11-30 20:52 ` Paul Bolle
2016-11-30 21:07 ` Jarod Wilson
2016-11-30 21:35 ` Jarod Wilson
2016-11-30 21:42 ` Paul Bolle [this message]
2016-11-30 21:57 ` Paul Bolle
2016-11-30 23:40 ` Jarod Wilson
2016-12-01 9:01 ` Paul Bolle
2016-12-01 13:46 ` Paul Bolle
2016-12-01 17:42 ` Nicolas Pitre
2016-12-01 20:15 ` Paul Bolle
2016-12-02 20:11 ` Nicolas Pitre
2016-12-02 22:41 ` Jarod Wilson
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=1480542127.27962.17.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=jarod@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®