All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: "Bryan O'Sullivan" <bos@pathscale.com>
Cc: rolandd@cisco.com, gregkh@suse.de, akpm@osdl.org,
	davem@davemloft.net, linux-kernel@vger.kernel.org,
	openib-general@openib.org
Subject: Re: [PATCH 8 of 20] ipath - sysfs support for core driver
Date: Thu, 09 Mar 2006 15:18:49 -0800	[thread overview]
Message-ID: <adapskvfbqe.fsf@cisco.com> (raw)
In-Reply-To: <ef8042c934401522ed3f.1141922821@localhost.localdomain> (Bryan O'Sullivan's message of "Thu,  9 Mar 2006 08:47:01 -0800")

 > +static ssize_t show_version(struct device_driver *dev, char *buf)
 > +{
 > +	return scnprintf(buf, PAGE_SIZE, "%s", ipath_core_version);
 > +}

Any reason you left a "\n" off of this attribute?

 > +static ssize_t show_atomic_stats(struct device_driver *dev, char *buf)
 > +{
 > +	memcpy(buf, &ipath_stats, sizeof(ipath_stats));
 > +
 > +	return sizeof(ipath_stats);
 > +}

I think putting a whole binary struct in a sysfs attribute is
considered a no-no.

 > +static ssize_t show_boardversion(struct device *dev,
 > +			       struct device_attribute *attr,
 > +			       char *buf)
 > +{
 > +	struct ipath_devdata *dd = dev_get_drvdata(dev);
 > +	return scnprintf(buf, PAGE_SIZE, "%s", dd->ipath_boardversion);
 > +}

Another missing "\n"

       reply	other threads:[~2006-03-09 23:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ef8042c934401522ed3f.1141922821@localhost.localdomain>
2006-03-09 23:18 ` Roland Dreier [this message]
2006-03-09 23:32   ` [PATCH 8 of 20] ipath - sysfs support for core driver Bryan O'Sullivan
2006-03-10  0:35     ` Revenge of the sysfs maintainer! (was Re: [PATCH 8 of 20] ipath - sysfs support for core driver) Greg KH
2006-03-10  0:46       ` Bryan O'Sullivan
2006-03-10  1:00         ` Greg KH
2006-03-10  4:58           ` Bryan O'Sullivan
2006-03-10  6:34             ` Greg KH
2006-03-10 15:53               ` Dave Jones
2006-03-10  7:57             ` Arjan van de Ven
2006-03-10 13:51               ` Bryan O'Sullivan
2006-03-10 14:06                 ` Arjan van de Ven
2006-03-10 15:55                   ` Bryan O'Sullivan
2006-03-10 16:24                     ` Arjan van de Ven
2006-03-10 16:36                       ` Bryan O'Sullivan
2006-03-10 16:41                         ` Arjan van de Ven
2006-03-10 16:25                     ` Dave Jones
2006-03-10 16:35                       ` Bryan O'Sullivan
2006-03-10 16:48                       ` Greg KH
2006-03-10 16:49                         ` Bryan O'Sullivan
2006-03-10 15:55                 ` Dave Jones
2006-03-10 13:58             ` [openib-general] " Talpey, Thomas
2006-03-09 23:46   ` [PATCH 8 of 20] ipath - sysfs support for core driver Greg KH
2006-03-09 23:48     ` Roland Dreier
2006-03-09 23:59     ` Bryan O'Sullivan
2006-03-10  1:02       ` Greg KH
2006-03-10  0:35 [PATCH 0 of 20] [RFC] ipath driver - another round for review Bryan O'Sullivan
2006-03-10  0:35 ` [PATCH 8 of 20] ipath - sysfs support for core driver Bryan O'Sullivan
2006-03-10  1:11   ` Greg KH
2006-03-10  5:09     ` Bryan O'Sullivan
2006-03-05  3:08       ` Pavel Machek
2006-03-10  6:37       ` Greg KH
2006-03-10 14:59         ` Roland Dreier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=adapskvfbqe.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=akpm@osdl.org \
    --cc=bos@pathscale.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=rolandd@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.