From: Michal Marek <mmarek@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Sam Ravnborg" <sam@ravnborg.org>,
"Aníbal Monsalve Salazar" <anibal@debian.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kbuild@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: linux-kbuild.git
Date: Thu, 26 Nov 2009 13:26:09 +0100 [thread overview]
Message-ID: <4B0E73E1.50900@suse.cz> (raw)
Hi Stephen,
I went through the patches posted to linux-kbuild and picked those that
were easy enough to review, looked safe and worked for me. I also took
Sam's series from kbuild-next.git, but I didn't really review it yet, so
there is no signoff from me (TBD). The repo is at
git://repo.or.cz/linux-kbuild.git for-next
Please ignore the other branches. The shortlog is
Jie Zhang (1):
net: add net_tstamp.h to headers_install
Jonathan Nieder (2):
scripts/package: add KBUILD_PKG_ROOTCMD variable
scripts/package: deb-pkg: use fakeroot if available
Michael Tokarev (1):
kbuild: fix bzImage build for x86
Michal Marek (2):
scripts/package: tar-pkg: use tar --owner=root
kbuild: create include/generated in silentoldconfig
Sam Ravnborg (14):
kbuild: search arch/$ARCH/include before include/
dontdiff: add generated
kbuild: move bounds.h to include/generated
kbuild: move asm-offsets.h to include/generated
ia64: move nr-irqs.h to include/generated
arm: move mach-types to include/generated
sh: move machtypes.h to include/generated
kbuild: drop include2/ used for O=... builds
kbuild: do not check for include/asm-$ARCH
kbuild: drop include/asm
kbuild: move compile.h to include/generated
drop explicit include of autoconf.h
kbuild: move autoconf.h to include/generated
kbuild: move utsrelease.h to include/generated
Wenji Huang (2):
Kbuild: clear marker out of modpost
Kbuild: clean up marker
There are some more patches on the mailing list and in -mm, which I'm
going to look at, but I think this should be a good start. What do you
think? Could this be added to linux-next?
Michal
next reply other threads:[~2009-11-26 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 12:26 Michal Marek [this message]
2009-11-26 19:37 ` linux-kbuild.git Sam Ravnborg
2009-11-27 4:22 ` linux-kbuild.git Stephen Rothwell
2009-11-27 9:42 ` linux-kbuild.git Michal Marek
2009-11-29 21:57 ` linux-kbuild.git Stephen Rothwell
2009-11-30 10:36 ` linux-kbuild.git Michal Marek
2009-12-02 6:25 ` linux-kbuild.git Stephen Rothwell
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=4B0E73E1.50900@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=anibal@debian.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
/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