mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Satyam Sharma <satyam@infradead.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make headers_check less chatty for success cases
Date: Tue, 31 Jul 2007 22:31:36 +0530 (IST)	[thread overview]
Message-ID: <alpine.LFD.0.999.0707312220570.28746@enigma.security.iitk.ac.in> (raw)
In-Reply-To: <1185899409.3083.122.camel@pmac.infradead.org>



On Tue, 31 Jul 2007, David Woodhouse wrote:

> On Tue, 2007-07-31 at 22:10 +0530, Satyam Sharma wrote:
> > "make headers_check" is too verbose. It likes to chat even if it has
> > just _successfully_ checked a header, and not just on seeing errors.
> > What is worse, even if you touch just one little header in some corner
> > (or possibly none) and type "make" on an "already-made" tree,
> > headers_check still feels obliged to check all the headers.
> 
> Didn't Sam have a better fix for that?

None that I see in kbuild.git, at least ... Anyway, now that I've silenced
headers_check, I keep seeing:

make[2]: `scripts/unifdef' is up to date.

which is because of the:

make -f scripts/Makefile.build obj=scripts scripts/unifdef
                       (passed separately) ^^^^^^^^^^^^^^^

from the top-level Makefile (scripts/Makefile says something about it
being built only on demand ...)

      parent reply	other threads:[~2007-07-31 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 16:40 Satyam Sharma
2007-07-31 16:30 ` David Woodhouse
2007-07-31 16:54   ` Sam Ravnborg
2007-07-31 17:01   ` Satyam Sharma [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=alpine.LFD.0.999.0707312220570.28746@enigma.security.iitk.ac.in \
    --to=satyam@infradead.org \
    --cc=dwmw2@infradead.org \
    --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

all inboxes | Powered by JetHome®