linux-kernel - Re: [PATCH] Make headers_check less chatty for success cases

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.0.999.0707312220570.28746@enigma.security.iitk.ac.in>
Date:	Tue, 31 Jul 2007 22:31:36 +0530 (IST)
From:	Satyam Sharma <satyam@...radead.org>
To:	David Woodhouse <dwmw2@...radead.org>
cc:	Sam Ravnborg <sam@...nborg.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Make headers_check less chatty for success cases



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 ...)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/