linux-kernel - Re: More effective processing (Re: [PATCH 25/33] kbuild: use POSIX BRE in headers install target)

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 21 Jul 2007 18:15:16 -0400
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	"Oleg Verych" <olecom@...wer.upol.cz>
Cc:	"Sam Ravnborg" <sam@...nborg.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	kbuild-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: More effective processing (Re: [PATCH 25/33] kbuild: use POSIX BRE in headers install target)

On 7/21/07, Oleg Verych <olecom@...wer.upol.cz> wrote:
> On Sat, Jul 21, 2007 at 10:39:16PM +0200, Sam Ravnborg wrote:
> > On Sat, Jul 21, 2007 at 03:21:43PM -0400, Mike Frysinger wrote:
> []
> > > while you could try and make a claim against memory/cpu effeciency, i
> > > fail to see how the first or last claims could possibly be backed up
>
> Less \{\(\\n\t\+\)\} [0] stuff make readings regex much easier. My
> confusion shows that i didn't used \{ much, because have another ways
> so far. And even after my quick testing i didn't realize that there
> was unrelated to main task whitespace cleanup.

the e-mail text you were quoting was [[:blank:]] vs [[:space:]], not + vs \{1,\}

> ./linux/stat.h:#if defined(__KERNEL__) || !defined(__GLIBC__) || (__GLIBC__ < 2)

__GLIBC__ cruft should be cleansed rather than looked at for anything else
-mike
-
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/