linux-kernel - Re: [RFC: Style] Kernel coding style for Extended Attributes.

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: <200906031211.49890.lkml@morethan.org>
Date:	Wed, 3 Jun 2009 12:11:47 -0500
From:	"Michael S. Zick" <lkml@...ethan.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC: Style] Kernel coding style for Extended Attributes.

On Wed June 3 2009, Linus Torvalds wrote:
> 
> On Wed, 3 Jun 2009, Michael S. Zick wrote:
> > 
> > Is there a recommended style for the kernel source?
> 
> I think the recommended style is:
> 
>   "Hide them behind a macro so that they never show up in the source".
>

That seems to be the general consensus in (/by) practice.

Thanks,
Mike  

> and then basically nobody will care about whether there is a space between 
> the __attribute__ and '(('.
> 
> 		Linus
> --
> 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/
> 
> 


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