linux-kernel - Re: what is the value of the macro "__setup

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] [day] [month] [year] [list]

Message-ID: <alpine.LFD.0.999.0708241650540.20322@enigma.security.iitk.ac.in>
Date:	Fri, 24 Aug 2007 16:59:15 +0530 (IST)
From:	Satyam Sharma <satyam@...radead.org>
To:	Paul Mundt <lethal@...ux-sh.org>
cc:	"Robert P. J. Day" <rpjday@...dspring.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: what is the value of the macro "__setup_param"?

On Fri, 24 Aug 2007, Paul Mundt wrote:
> 
> > > > include/linux/init.h:#define __setup_param(str, unique_id, fn, early)      \
> > > > include/linux/init.h:#define __setup_param(str, unique_id, fn)  /* nothing */
> 
> Notice the problem now? :-)

We should probably keep it that way. I don't see why anybody should be
using __setup_param directly anyway, so this becomes a nice build-time
error to flag such errant usage :-)

Seriously speaking, though, we should probably just get rid of that
wrong line. It's just an init.h-internal macro to be used by early_param
and __setup, and because those are themselves empty when MODULE, there's
no issues in removing the (unused, broken) __setup_param either.
-
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/