From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266832AbUHISQv (ORCPT ); Mon, 9 Aug 2004 14:16:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266816AbUHISOE (ORCPT ); Mon, 9 Aug 2004 14:14:04 -0400 Received: from fw.osdl.org ([65.172.181.6]:36584 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S266815AbUHISNC (ORCPT ); Mon, 9 Aug 2004 14:13:02 -0400 Date: Mon, 9 Aug 2004 10:51:13 -0700 From: "Randy.Dunlap" To: Hollis Blanchard Cc: linux-kernel@vger.kernel.org, viro@parcelfarce.linux.theplanet.co.uk Subject: Re: [RFC] Host Virtual Serial Interface driver Message-Id: <20040809105113.4923342d.rddunlap@osdl.org> In-Reply-To: <1091827384.31867.21.camel@localhost> References: <1091827384.31867.21.camel@localhost> Organization: OSDL X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i686-pc-linux-gnu) X-Face: +5V?h'hZQPB9kW Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 06 Aug 2004 16:23:05 -0500 Hollis Blanchard wrote: | Hi, I have a new char driver I'd like to get comments on. It is specific | to IBM's p5 server line; I've included a description from the comments | here: ... | I've included the whole file below; it's pretty much self-contained. All | comments welcome. | | -- | | #include | #include | #include | #include | #include | #include | #include | #include | #include | #include | #include | #include | #include | #include To the extent possible, we like to put the linux/* files in alpha order, and same with the asm/* files. Separately, as you have them. | #include | #include | #include | #include | #include | | #define __ALIGNED__ __attribute__((__aligned__(sizeof(long)))) You should explain this bit (__ALIGNED__). | static inline int hdrlen(const uint8_t *packet) | { | const int lengths[] = { 4, 6, 6, 8, }; | struct hvsi_header *header = (struct hvsi_header *)packet; | | return lengths[VS_DATA_PACKET_HEADER - header->type]; | } Any chance of bad data (value) in header->type ? | if (hangup) { | tty_hangup(hangup); | } extra braces (style); maybe in a few other places also. -- ~Randy