WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] 1 of 2: default ssid to 0

To: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] 1 of 2: default ssid to 0
From: aq <aquynh@xxxxxxxxx>
Date: Sun, 26 Jun 2005 19:07:40 +0900
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Stefan Berger <stefanb@xxxxxxxxxx>
Delivery-date: Sun, 26 Jun 2005 10:06:35 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PCIz4iqDq20n/fTz6RhJ8vc2HYz/a3Ld/y2lr4yrBb9q5qKoZ1i6gD5XY8S+MXrW2co9xCJi5gJFJqUnAiWwry08nCpiP7kcqlZ/jMIaE2eZgMO/mNGCEkUt7tpTAqxx7e3++/CMV9MNf9oFPB/7k3UbXgsSmxq3z4Ri6cp/kqw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200506260324.27847.mark.williamson@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <OFC7293D35.7F7078B7-ON8525702B.00641461-8525702B.006592BC@xxxxxxxxxx> <200506260249.18338.mark.williamson@xxxxxxxxxxxx> <9cde8bff05062519186af4a17@xxxxxxxxxxxxxx> <200506260324.27847.mark.williamson@xxxxxxxxxxxx>
Reply-to: aq <aquynh@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 6/26/05, Mark Williamson <mark.williamson@xxxxxxxxxxxx> wrote:
> > i think it is very bad idea to have 2 coding styles for code in kernel
> > and out of kernel. because people work on all those code must always
> > remember to adjust the editor configuration, depend on the code in or
> > out of kernel, which is a nightmare :-(
> 
> Yes, it's an extra thing to think about.  It also means that code imported
> from Linux needs adjusting to fit with the Xen coding convention.
> 
> OTOH, we don't just work with the Linux kernel any more, so there will be
> multiple coding conventions anyhow.  I just set up emacs so I can type "M-x
> xen-c-mode" or "M-x linux-c-mode".
> 
> > how about this simple guide?
> > - C code complies Linux kernel coding style
> 
> I don't think this is likely to happen any time soon - it'd require patches to
> all of Xen and the tools :-( (and probably to some of the Linux code but
> that's arguably desirable)
> 

yes, that is too bad. but at least if we have an official style, we
can enforce the rules *from now on*. the old code can be fix later (if
possible).

regards,
aq

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel