From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ak@linux.intel.com, daniel.santos@pobox.com, kliegs@chromium.org,
ozancag@gmail.com, urpapa@gmail.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT] kbuild changes for v3.7
Date: Thu, 11 Oct 2012 23:56:04 +0200 [thread overview]
Message-ID: <20121011215604.GA6652@sepie.suse.cz> (raw)
Hi Linus,
The main part of kbuild for v3.7 contains:
* Fix for scripts/Makefile.modpost to not choke on a '.ko' substring in
the build directory path
* Two warning fixes (modpost and main Makefile)
* __compiletime_error works also with gcc 4.3
* make tar{gz,bz2,xz}-pkg uses default compression settings instead of
saving as many bytes as possible (this should actually be in the misc
branch, I don't know why I applied it here).
Michal
The following changes since commit 0d7614f09c1ebdbaa1599a5aba7593f147bf96ee:
Linux 3.6-rc1 (2012-08-02 16:38:10 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git kbuild
for you to fetch changes up to 415c2c525fab214ab75413aadbc67b4ee9cf212e:
compiler-gcc4.h: correct verion check for __compiletime_error (2012-10-11 22:51:41 +0200)
----------------------------------------------------------------
Andi Kleen (1):
Kbuild: use normal compression settings for tar*-pkg
Daniel Santos (1):
compiler-gcc4.h: correct verion check for __compiletime_error
Jonathan Kliegman (1):
modpost: Permit .GCC.command.line sections
Ozan Çağlayan (1):
kbuild: Remove useless warning while appending KCFLAGS
이건호 (1):
scripts/Makefile.modpost: error in finding modules from .mod files.
Makefile | 19 +++----------------
include/linux/compiler-gcc4.h | 2 +-
scripts/Makefile.modinst | 2 +-
scripts/Makefile.modpost | 2 +-
scripts/mod/modpost.c | 1 +
scripts/package/buildtar | 6 +++---
6 files changed, 10 insertions(+), 22 deletions(-)
reply other threads:[~2012-10-11 21:56 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=20121011215604.GA6652@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=ak@linux.intel.com \
--cc=daniel.santos@pobox.com \
--cc=kliegs@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ozancag@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=urpapa@gmail.com \
/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®