From: Sam Ravnborg <sam@ravnborg.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Manuel Lauss <mano@roarinelk.homelinux.net>,
Jean Delvare <khali@linux-fr.org>,
Anders Kaseorg <andersk@mit.edu>,
Sean MacLennan <smaclennan@pikatech.com>
Subject: [GIT] kbuild fixes
Date: Tue, 5 May 2009 21:04:16 +0200 [thread overview]
Message-ID: <20090505190416.GA19475@uranus.ravnborg.org> (raw)
Hi Linus.
This fixes an annoying warning "unexpected non-allocatable section",
that shows up in certain combinations of targets/gccs.
The tree commit fixes three different sources of the warnings.
This has now been in -next for a day or two with no additional comlains.
Please pull.
Sam
The following changes since commit b4348f32dae3cb6eb4bc21c7ed8f76c0b11e9d6a:
Linus Torvalds (1):
Merge branch 'for-linus' of git://oss.sgi.com/xfs/xfs
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-fixes.git master
Anders Kaseorg (1):
kbuild, modpost: fix unexpected non-allocatable section when cross compiling
Sam Ravnborg (2):
kbuild, modpost: fix "unexpected non-allocatable" warning with SUSE gcc
kbuild, modpost: fix unexpected non-allocatable warning with mips
scripts/mod/modpost.c | 47 ++++++++++++++++++++++++++++++++++-------------
1 files changed, 34 insertions(+), 13 deletions(-)
next reply other threads:[~2009-05-05 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 19:04 Sam Ravnborg [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-20 20:35 [GIT] kbuild fixes Sam Ravnborg
2010-06-11 13:59 Michal Marek
2012-10-07 15:53 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=20090505190416.GA19475@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=andersk@mit.edu \
--cc=khali@linux-fr.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mano@roarinelk.homelinux.net \
--cc=smaclennan@pikatech.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