From: Greg KH <greg@kroah.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 - sysfs sensor nameing inconsistency
Date: Sat, 16 Aug 2003 09:50:16 -0700 [thread overview]
Message-ID: <20030816165016.GE9735@kroah.com> (raw)
In-Reply-To: <200308161938.47935.arvidjaar@mail.ru>
On Sat, Aug 16, 2003 at 07:38:47PM +0400, Andrey Borzenkov wrote:
> On Saturday 16 August 2003 00:51, Greg KH wrote:
> > On Sat, Jul 26, 2003 at 10:00:51PM +0400, Andrey Borzenkov wrote:
> > > 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.
> > >
> > > Assuming this patch (or variant thereof) is accepted I can then produce
> > > libsensors patch that will easily reuse current sensors.conf. I have
> > > already done it for gkrellm and as Mandrake is going to include 2.6 in
> > > next release sensors support becomes more of an issue.
> >
> > I like this idea, but now that the name logic has changed in the i2c
> > code, care to re-do this patch? Just set the name field instead of
> > creating a new file in sysfs.
> >
>
> something like attached patch? I like it as well :)
Why rename local variables? Your patch would be a lot smaller if you
just keep the same local name variable, and fix up the name strings.
> note that in 2.6.0-test3 name in sysfs is empty. I had to add a chunk to
> i2c-core to at least test my patch. or may be I misunderstood how
> client->name is used.
No, you are correct. I've added the name info back in the -bk tree
right now. Try 2.6.0-test3-bk4 for the proper usage.
thanks,
greg k-h
next prev parent reply other threads:[~2003-08-16 16:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 18:14 2.6 - sysfs sensor nameing inconsistency 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 [this message]
2003-08-18 16:49 ` Andrey Borzenkov
2003-08-18 21:31 ` Greg KH
2005-05-19 6:24 ` Greg KH
2003-08-19 19:19 ` Andrey Borzenkov
2003-08-19 19:45 ` Greg KH
2005-05-19 6:24 ` Greg KH
2003-08-31 16:25 ` Andrey Borzenkov
2005-05-19 6:24 ` Andrey Borzenkov
2003-09-22 22:29 ` Greg KH
2005-05-19 6:24 ` Greg KH
2003-11-02 18:50 ` Andrey Borzenkov
2005-05-19 6:24 ` Andrey Borzenkov
-- strict thread matches above, loose matches on Subject: below --
2003-07-27 4:42 Margit Schubert-While
2003-07-27 6:23 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=20030816165016.GE9735@kroah.com \
--to=greg@kroah.com \
--cc=arvidjaar@mail.ru \
--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 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.