linux-kernel - Re: [RFC][PATCH] A generic boolean (version 4)

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:	Sun, 23 Jul 2006 21:46:36 +0200
From:	ricknu-0@...dent.ltu.se
To:	Michael Buesch <mb@...sch.de>
Cc:	Andrew Morton <akpm@...l.org>, Jeff Garzik <jeff@...zik.org>,
	Alexey Dobriyan <adobriyan@...il.com>,
	Vadim Lobanov <vlobanov@...akeasy.net>,
	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Shorty Porty <getshorty_@...mail.com>,
	Peter Williams <pwil3058@...pond.net.au>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Stefan Richter <stefanr@...6.in-berlin.de>, larsbj@...lik.net,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] A generic boolean (version 4)

Citerar Michael Buesch <mb@...sch.de>:

> On Sunday 23 July 2006 17:49, ricknu-0@...dent.ltu.se wrote:
> > And here comes lucky number four.
> 
> > diff --git a/include/asm-i386/types.h b/include/asm-i386/types.h
> > index 4b4b295..3cb84ac 100644
> > --- a/include/asm-i386/types.h
> > +++ b/include/asm-i386/types.h
> > @@ -1,6 +1,8 @@
> >  #ifndef _I386_TYPES_H
> >  #define _I386_TYPES_H
> >  
> > +typedef _Bool bool;
> > +
> >  #ifndef __ASSEMBLY__
> 
> I'd say that typedef must go into the !__ASSEMBLY__ section here,
> like the other typedefs in that header.

You are right. Misstook the #endif as #else (a downside of programming late).
It is corrected, thanks.

> Greetings Michael.

See ya
/Richard
-
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/