From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265987AbUGILYi (ORCPT ); Fri, 9 Jul 2004 07:24:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265993AbUGILYi (ORCPT ); Fri, 9 Jul 2004 07:24:38 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:18636 "EHLO scrub.home") by vger.kernel.org with ESMTP id S265987AbUGILYh (ORCPT ); Fri, 9 Jul 2004 07:24:37 -0400 Date: Fri, 9 Jul 2004 13:23:16 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: Linus Torvalds cc: Miles Bader , "David S. Miller" , Herbert Xu , chrisw@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org, sds@epoch.ncsc.mil, jmorris@redhat.com, mika@osdl.org Subject: Re: [PATCH] Use NULL instead of integer 0 in security/selinux/ In-Reply-To: Message-ID: References: <20040707122525.X1924@build.pdx.osdl.net> <20040707202746.1da0568b.davem@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.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