linux-kernel - Re: [PATCH 01/12] making the kernel -Wshadow clean

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]

Message-Id: <20060730120631.9ee1ab09.akpm@osdl.org>
Date:	Sun, 30 Jul 2006 12:06:31 -0700
From:	Andrew Morton <akpm@...l.org>
To:	"Jesper Juhl" <jesper.juhl@...il.com>
Cc:	pj@....com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/12] making the kernel -Wshadow clean - fix mconf

On Sun, 30 Jul 2006 20:48:23 +0200
"Jesper Juhl" <jesper.juhl@...il.com> wrote:

> > Perhaps I am misreading this patch set?
> >
> i don't think you are. It's just that I want to take the least
> intrusive route *now*, make us -Wshadow clean, get -Wshadow to be an
> accepted part of the Makefile, *then* deal with the more
> intrusive/controversial renamings, where I guess you'd have done
> things in the opposite order - right?

yup.  Experience tells us that it's better to get things right first time,
because we don't get around to doing the intended second pass (looks at
lock_cpu_hotplug())

That being said, no, we can't go and rename up().  Let us go through the
patches one-at-a-time..
-
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/