From: Sam Ravnborg <sam@ravnborg.org>
To: linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [GIT] kbuild fixes that needs some testing
Date: Wed, 14 Jan 2009 21:52:08 +0100 [thread overview]
Message-ID: <20090114205208.GA4076@uranus.ravnborg.org> (raw)
I plan to ask Linus to pull kbuild-fixes.git soon as it reverts the
commits that introduces the problems with distcc, too large modules etc.
The pull request are below.
I has been in the work for too long but as my current setup
is br0ken(*) then I need someone to pull the tree and check
if it builds etc.
I had hoped to find time to test this myself but thats not this week.
(*) Motherboard on my primary linux box is dead and the box I use
atm is far away from decent...
Sam
The following changes since commit a6525042bfdfcab128bd91fad264de10fd24a55e:
Linus Torvalds (1):
Merge branch 'x86-pat-for-linus' of git://git.kernel.org/.../tip/linux-2.6-tip
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-fixes.git master
Andi Kleen (1):
kbuild: print usage with no arguments in scripts/config
Randy Dunlap (1):
kbuild: fix kbuild.txt typos
Sam Ravnborg (1):
Revert "kbuild: strip generated symbols from *.ko"
Documentation/kbuild/kbuild.txt | 29 +++---
Makefile | 59 ++++--------
arch/x86/scripts/strip-symbols | 1 -
init/Kconfig | 7 --
kernel/kallsyms.c | 16 ++-
scripts/Makefile.build | 55 ++++-------
scripts/Makefile.modinst | 3 +-
scripts/config | 4 +
scripts/genksyms/genksyms.c | 21 +---
scripts/genksyms/keywords.c_shipped | 189 +++++++++++++++++------------------
scripts/genksyms/keywords.gperf | 2 -
scripts/kallsyms.c | 21 +++--
scripts/mksysmap | 7 +-
scripts/strip-symbols | 22 ----
14 files changed, 185 insertions(+), 251 deletions(-)
delete mode 100644 arch/x86/scripts/strip-symbols
delete mode 100644 scripts/strip-symbols
reply other threads:[~2009-01-14 20:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090114205208.GA4076@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®