public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	jdike@addtoit.com, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fallout from kbuild changes
Date: Fri, 20 Jul 2007 10:20:29 +0100	[thread overview]
Message-ID: <20070720092029.GE21668@ftp.linux.org.uk> (raw)
In-Reply-To: <20070720064049.GA19653@uranus.ravnborg.org>

BTW, the presense of vmlinux in the second modpost generates warnings
in two cases - i386 with CONFIG_RELOCATABLE and sparc32 (always).
The warnings tend to be bogus.  Do we really want them there now that
we should (in theory) get all useful stuff from vmlinux.o?  Other
targets get aways with that since they don't have relocs survive into
vmlinux...

  reply	other threads:[~2007-07-20  9:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20  1:01 [PATCH] fallout from kbuild changes Al Viro
2007-07-20  6:40 ` Sam Ravnborg
2007-07-20  9:20   ` Al Viro [this message]
2007-07-20 11:36     ` Sam Ravnborg
2007-07-20 14:09 ` Jeff Dike

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=20070720092029.GE21668@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=jdike@addtoit.com \
    --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