public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: JBeulich@novell.com, amwang@redhat.com, mmarek@suse.cz,
	sam@ravnborg.org, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT] kbuild fixes for 2.6.36-rc2
Date: Sat, 21 Aug 2010 22:13:50 +0200	[thread overview]
Message-ID: <20100821201350.GA9144@sepie.suse.cz> (raw)

Hi Linus,

there are some post-rc1 kbuild fixes:
* Two kconfig fixes by Sam.
* A fix for new make version by Jan (this is technically no a rc1
  regression, but we should fix it sooner rather than later).
* Two setlocalversion fixes, one by Amerigo, one by me.

Thanks,
Michal


The following changes since commit da5cabf80e2433131bf0ed8993abc0f7ea618c73:

  Linux 2.6.36-rc1 (2010-08-15 17:41:37 -0700)

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

Amerigo Wang (1):
      makefile: not need to regenerate kernel.release file when make kernelrelease

Jan Beulich (1):
      fixes for using make 3.82

Michal Marek (2):
      Merge commit 'v2.6.36-rc1' into kbuild/rc-fixes
      setlocalversion: Ignote SCMs above the linux source tree

Sam Ravnborg (2):
      kconfig: fix savedefconfig with choice marked optional
      kconfig: fix segfault when detecting recursive dependency

 Makefile                   |    4 ++--
 firmware/Makefile          |    2 +-
 scripts/kconfig/confdata.c |    6 ++++--
 scripts/kconfig/symbol.c   |    2 ++
 scripts/mkmakefile         |    4 +++-
 scripts/setlocalversion    |    4 ++--
 6 files changed, 14 insertions(+), 8 deletions(-)

             reply	other threads:[~2010-08-23  9:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-21 20:13 Michal Marek [this message]
2010-08-23 10:56 ` [GIT] kbuild fixes for 2.6.36-rc2 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=20100821201350.GA9144@sepie.suse.cz \
    --to=mmarek@suse.cz \
    --cc=JBeulich@novell.com \
    --cc=amwang@redhat.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --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