linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: margitsw@t-online.de (Margit Schubert-While)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6 - sysfs sensor nameing inconsistency
Date: Sun, 27 Jul 2003 06:42:12 +0200	[thread overview]
Message-ID: <5.1.0.14.2.20030727061608.00a77960@pop.t-online.de> (raw)

 > Attached is patch against 2.6.0-test1 that adds type_name to all in-tree
 > sensors; it sets it to the same values as corr. 2.4 senors and (in one case)
 > changes client name to match that of 2.4.

Well, it certainly doesn't with the lm85.c  :-)
Hint - names are in lib/chips.h in sensors package :-)

Although, I will be working over lm85.c in the next week or so.

 > +static const char *type_name = "";
 > +static ssize_t show_type_name(struct device *dev, char *buf)
 > +{
 > + return sprintf(buf, "%s\n", type_name);
 > +}
 > +static DEVICE_ATTR(type_name, S_IRUGO, show_type_name, NULL);

 > - const char *type_name = "";

 > + device_create_file(&new_client->dev, &dev_attr_type_name);



Margit 


             reply	other threads:[~2003-07-27  4:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-27  4:42 Margit Schubert-While [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-27  6:23 2.6 - sysfs sensor nameing inconsistency Andrey Borzenkov
2003-07-15 18:14 Andrey Borzenkov
2003-07-15 20:18 ` Greg KH
2003-07-26 18:00   ` Andrey Borzenkov
2003-08-15 20:51     ` Greg KH
2003-08-16 15:38       ` Andrey Borzenkov
2003-08-16 16:50         ` Greg KH
2003-08-18 16:49           ` Andrey Borzenkov
2003-08-18 21:31             ` Greg KH
2003-08-19 19:19           ` Andrey Borzenkov
2003-08-19 19:45             ` Greg KH
2003-08-31 16:25               ` Andrey Borzenkov
2003-09-22 22:29                 ` Greg KH
2003-11-02 18:50                   ` Andrey Borzenkov

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=5.1.0.14.2.20030727061608.00a77960@pop.t-online.de \
    --to=margitsw@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).