The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org, sam@ravnborg.org
Subject: Re: [patch 2.6.12-rc5] Stop arch/i386/kernel/vsyscall-note.o being rebuilt every time
Date: Mon, 06 Jun 2005 00:11:11 -0400	[thread overview]
Message-ID: <42A3CCDF.7000701@pobox.com> (raw)
In-Reply-To: <615.1118029984@kao2.melbourne.sgi.com>

Keith Owens wrote:
> arch/i386/kernel/vsyscall-note.o is not listed as a target so its .cmd
> file is neither considered as a target nor is it read on the next
> build.  This causes vsyscall-note.o to be rebuilt every time that you
> run make, which causes vmlinux to be rebuilt every time.
> 
> Signed-off-by: Keith Owens <kaos@ocs.com.au>

Nice, thanks.  That always annoyed me.

	Jeff



      reply	other threads:[~2005-06-06  4:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-06  3:53 [patch 2.6.12-rc5] Stop arch/i386/kernel/vsyscall-note.o being rebuilt every time Keith Owens
2005-06-06  4:11 ` Jeff Garzik [this message]

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=42A3CCDF.7000701@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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