All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Anders Kaseorg <andersk@mit.edu>, Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Lots of unexpected non-allocatable section warnings
Date: Sun, 3 May 2009 11:05:17 +0200	[thread overview]
Message-ID: <20090503110517.6d09bca2@hyperion.delvare> (raw)

Hi Anders, Sam,

After your fix "kbuild, modpost: Check the section flags, to catch
missing ax/aw", I get a lot of warnings like the following during
modpost on x86-64:

WARNING: arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.o (.comment.SUSE.OPTs): unexpected non-allocatable section.
Did you forget to use "ax"/"aw" in a .S file?
Note that for example <linux/init.h> contains
section definitions for use in .S files.

Apparently there's one such warning for every module on my system, that
is, 907. That's a lot, and pretty annoying. How do I solve this? I don't
know much about assembly.

Thanks,
-- 
Jean Delvare

             reply	other threads:[~2009-05-03  9:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-03  9:05 Jean Delvare [this message]
2009-05-03 10:30 ` Lots of unexpected non-allocatable section warnings Sam Ravnborg
2009-05-03 10:42   ` Stephen Rothwell
2009-05-03 18:07     ` [PATCH] modpost: more complete endianness fixing Anders Kaseorg
2009-05-03 19:48       ` Sam Ravnborg
2009-05-04  8:00         ` Jean Delvare
2009-05-03 10:48   ` Lots of unexpected non-allocatable section warnings Jean Delvare
2009-05-03 18:03     ` Sam Ravnborg
2009-05-03 20:29       ` Sam Ravnborg
2009-05-04  7:58         ` Jean Delvare
2009-05-04  9:51           ` Sam Ravnborg
2009-05-04  8:28         ` Manuel Lauss
2009-05-04  9:49           ` Sam Ravnborg
2009-05-04  9:49             ` Sam Ravnborg
2009-05-04 10:05             ` Manuel Lauss
2009-05-04 15:24             ` David Daney
2009-05-04 15:26           ` David Daney
2009-05-03 18:18     ` Andreas Schwab

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=20090503110517.6d09bca2@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=andersk@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.