mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: fernando@oss.ntt.co.jp, jason.wessel@windriver.com,
	mmarek@suse.cz, swarren@nvidia.com, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT] kbuild changes for v3.3-rc1
Date: Mon, 16 Jan 2012 21:48:20 +0100	[thread overview]
Message-ID: <20120116204819.GA4562@sepie.suse.cz> (raw)

Hi Linus,

the main part of kbuild is a bit boring this time. The dtc tool got the
ability to record dependency information and kbuild makes use of it,
plus there are three minor fixes.

Michal

The following changes since commit 1ea6b8f48918282bdca0b32a34095504ee65bab5:

  Linux 3.2-rc1 (2011-11-07 16:16:02 -0800)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git kbuild

Fernando Luis Vázquez Cao (1):
      scripts/genksyms: clean lex/yacc generated files

Jason Wessel (1):
      kbuild: Correctly deal with make options which contain an "s"

Michal Marek (1):
      kbuild: Fix comment in Makefile.lib

Stephen Warren (2):
      dtc: Implement -d option to write out a dependency file
      Kbuild: Use dtc's -d (dependency) option

 Makefile                      |    2 +-
 arch/arm/boot/Makefile        |    6 ++++--
 arch/microblaze/boot/Makefile |    2 +-
 arch/openrisc/boot/Makefile   |    4 ++--
 arch/powerpc/boot/Makefile    |    4 ++--
 scripts/Makefile.lib          |    8 ++++----
 scripts/dtc/dtc.c             |   21 ++++++++++++++++++++-
 scripts/dtc/srcpos.c          |    4 ++++
 scripts/dtc/srcpos.h          |    1 +
 scripts/genksyms/Makefile     |    1 +
 10 files changed, 40 insertions(+), 13 deletions(-)

                 reply	other threads:[~2012-01-16 20:48 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=20120116204819.GA4562@sepie.suse.cz \
    --to=mmarek@suse.cz \
    --cc=fernando@oss.ntt.co.jp \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@nvidia.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

all inboxes | Powered by JetHome®