Re: [PATCH] Use NULL instead of integer 0 in security/selinux/
[Posted July 14, 2004 by corbet]
| From: |
| Roman Zippel <zippel-AT-linux-m68k.org> |
| To: |
| Linus Torvalds <torvalds-AT-osdl.org> |
| Subject: |
| Re: [PATCH] Use NULL instead of integer 0 in security/selinux/ |
| Date: |
| Fri, 9 Jul 2004 13:23:16 +0200 (CEST) |
| Cc: |
| Miles Bader <miles-AT-gnu.org>, "David S. Miller" <davem-AT-redhat.com>,
Herbert Xu <herbert-AT-gondor.apana.org.au>, chrisw-AT-osdl.org,
akpm-AT-osdl.org, linux-kernel-AT-vger.kernel.org, sds-AT-epoch.ncsc.mil,
jmorris-AT-redhat.com, mika-AT-osdl.org |
Hi,
On Thu, 8 Jul 2004, Linus Torvalds wrote:
> I have one. It's in my head. It's called the Linux Kernel C standard. Some
> of it is documented in CodinggStyle, others is just codified in existing
> practice.
So far we have been quite liberal in style questions, what annoys me here
is that people send warning patches directly to you without even notifying
the maintainers. If you want people to conform people to a certain
CodingStyle please document officially in the kernel, sparse isn't
distributed with the kernel and the sparse police is silently changing the
kernel all over the place with sometimes questionable benefit. Only the
__user warnings had really found the bugs, but the rest I've seen changes
perfectly legal code.
bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
