mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Mike Frysinger <vapier@gentoo.org>, WANG Cong <amwang@redhat.com>
Subject: [GIT] kbuild fixes
Date: Sat, 20 Jun 2009 13:44:11 +0200	[thread overview]
Message-ID: <20090620114411.GA32531@uranus.ravnborg.org> (raw)

Hi Linus.

This tree has seen no testing - but the individual patches
has been tested. I decided to request a pull early because
the kallsyms bug annoys several people.

Please pull to fix:

- kallsyms fix
  fix build breakage on arm
  fix backtrace on at least sparc and presumeably also x86

- make htmldocs breakage

- 2 fixlets for kernel-doc

The following changes since commit fb20871a54961b82d35303b43452928186c1361d:
  Linus Torvalds (1):
        Merge git://git.kernel.org/.../gregkh/staging-2.6

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-fixes.git master

Amerigo Wang (1):
      kbuild: fix build error during make htmldocs

Mike Frysinger (1):
      kallsyms: fix inverted valid symbol checking

Randy Dunlap (2):
      kernel-doc: ignore kmemcheck_bitfield_begin/end
      kernel-doc: fix param matching for array params

 scripts/basic/docproc.c |    2 +-
 scripts/kallsyms.c      |    6 +++---
 scripts/kernel-doc      |   19 +++++++++++++++++++
 3 files changed, 23 insertions(+), 4 deletions(-)

             reply	other threads:[~2009-06-20 11:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-20 11:44 Sam Ravnborg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-10-07 15:53 Michal Marek
2010-06-11 13:59 Michal Marek
2009-07-20 20:35 Sam Ravnborg
2009-07-03 21:43 Sam Ravnborg
2009-07-03 21:53 ` Floris Kraak
2009-05-05 19:04 Sam Ravnborg

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=20090620114411.GA32531@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=amwang@redhat.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vapier@gentoo.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

Powered by JetHome