linux-kernel - Re: [patch, -git] isdn: hysdn

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:	Wed, 30 Apr 2008 12:24:47 -0700
From:	Harvey Harrison <harvey.harrison@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	"Denis V. Lunev" <den@...nvz.org>, mingo@...e.hu,
	linux-kernel@...r.kernel.org
Subject: Re: [patch, -git] isdn: hysdn_procconf.c build fix

On Wed, 2008-04-30 at 12:14 -0700, Andrew Morton wrote:
> On Wed, 30 Apr 2008 23:03:05 +0400
> "Denis V. Lunev" <den@...nvz.org> wrote:
> > > 
> > > allmodconfig is for one thing and one thing only: compilation coverage
> > > testing.  If there is anything which is not compiled after `make
> > > allmodconfig' then that's a bug.
> > > 
> > > But how to fix it?  Perhaps we need to add a CONFIG_ALLFOOCONFIG which can
> > > be tested at the appropriate places.
> > 
> > I think that the same should be applied to allyesconfig
> 
> That's what ALLFOOCONFIG refers to ;)
> 
> There _might_ be a need to discriminate between allyesconfig and
> allmodconfig, but usually not, I expect.
> 
> Perhaps we should implement CONFIG_ALLYESCONFIG, CONFIG_ALLMODCONFIG and
> CONFIG_ALLFOOCONFIG, where
> 
> 	ALLFOOCONFIG = ALLYESCONFIG || ALLMODCONFIG
> 	
> (where FOO is renamed to something sensible, but what?)

ALLBUILDCONFIG

Harvey

--
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/