Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261522AbVBRVbB (ORCPT ); Fri, 18 Feb 2005 16:31:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261521AbVBRV3o (ORCPT ); Fri, 18 Feb 2005 16:29:44 -0500 Received: from mail.kroah.org ([69.55.234.183]:414 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S261520AbVBRV3c (ORCPT ); Fri, 18 Feb 2005 16:29:32 -0500 Date: Fri, 18 Feb 2005 12:05:52 -0800 From: Greg KH To: Christoph Hellwig , mike.miller@hp.com, linux-kernel@vger.kernel.org, mochel@osdl.org, akpm@osdl.org, eric.moore@lsil.com, linux-scsi@vger.kernel.org Subject: Re: cciss CSMI via sysfs for 2.6 Message-ID: <20050218200552.GC20171@kroah.com> References: <20050216164512.GA5734@beardog.cca.cpqcorp.net> <20050218194628.GA24583@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050218194628.GA24583@infradead.org> User-Agent: Mutt/1.5.8i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1063 Lines: 29 On Fri, Feb 18, 2005 at 07:46:28PM +0000, Christoph Hellwig wrote: > > /* > > + * sysfs stuff > > + * this should be moved to it's own file, maybe cciss_sysfs.h > > + */ > > + > > +static ssize_t cciss_firmver_show(struct device *dev, char *buf) > > +{ > > + ctlr_info_t *h = dev->driver_data; > > + return sprintf(buf,"%c%c%c%c\n", h->firm_ver[0], h->firm_ver[1], > > + h->firm_ver[2], h->firm_ver[3]); > > +} > > I really wish we had a common firmver release attribut in the driver > core, as mentioned in the fc transport class thread. Greg? For a device? It seems a huge overkill to add this attribute for _every_ device in the system, when only a small minority can actually use it. Just put it as a default scsi or transport class attribute instead. thanks, greg k-h - 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/