From: mds@paradyne.com (Mark D. Studebaker)
To: lm-sensors@vger.kernel.org
Subject: two patches
Date: Thu, 19 May 2005 06:23:35 +0000 [thread overview]
Message-ID: <3D322847.28D5DDEA@paradyne.com> (raw)
In-Reply-To: <20020715003408.7c5513a4.khali@linux-fr.org>
I checked in the first one. Good catch.
Not really dangerous because the file modes in /proc of course
overrule whatever's in the library.
Let's hold off on the sensors change until after the release.
mds
Jean Delvare wrote:
>
> Hello
>
> Here are two patches for lm_sensors2 I wrote in the train two hours ago.
>
> The first one fixes a (maybe dangerous) bug in libsensors where
> read-only features could be written and write-only features could be
> read.
>
> The second one simply (re)indents the eeprom section of prog/sensors. I
> plan to make modifications on this part soon, and it was hardly readable
> the way it was before.
>
> --
> Jean "Khali" Delvare
> http://www.ensicaen.ismra.fr/~delvare/
>
>
> Name: lm_sensors-and.diff
> lm_sensors-and.diff Type: Plain Text (text/plain)
> Encoding: base64
>
> Name: lm_sensors-indent-eeprom.diff
> lm_sensors-indent-eeprom.diff Type: Plain Text (text/plain)
> Encoding: base64
next prev parent reply other threads:[~2005-05-19 6:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:23 two patches Jean Delvare
2005-05-19 6:23 ` Mark D. Studebaker [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-16 5:50 Yury G. Kudryashov
2010-04-16 15:28 ` Dan Nicholson
2010-04-16 16:31 ` Kay Sievers
2010-04-16 17:34 ` Dan Nicholson
2010-04-16 17:51 ` Yury G. Kudryashov
2010-04-16 18:03 ` Dan Nicholson
2010-04-16 18:52 ` Yury G. Kudryashov
2010-04-16 18:56 ` Yury G. Kudryashov
2010-04-16 19:01 ` Yury G. Kudryashov
2010-04-16 22:01 ` Dan Nicholson
2010-04-16 22:02 ` Dan Nicholson
2002-04-11 13:22 Two patches Grigory Batalov
2002-04-11 13:33 ` Grigory Batalov
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=3D322847.28D5DDEA@paradyne.com \
--to=mds@paradyne.com \
--cc=lm-sensors@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.