linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Matthew <jackdachef@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.25
Date: Sat, 19 Apr 2008 10:17:01 +0400	[thread overview]
Message-ID: <20080419061701.GA7688@cvg> (raw)
In-Reply-To: <480964F7.3040701@keyaccess.nl>

[Rene Herman - Sat, Apr 19, 2008 at 05:20:23AM +0200]
> On 19-04-08 05:05, Rene Herman wrote:
>> On 18-04-08 22:03, Cyrill Gorcunov wrote:
>>> | it seems drivers/acpi/thermal.c has a small nit
>>> | | 881:    /* sys I/F for generic thermal sysfs support */
>>> | 882:    #define KELVIN_TO_MILLICELSIUS(t) (t * 100 - 273200)
>>> | | but it should multiply by 1000 meguess
>>> |
>>> oh, i'm wrong, sorry
>> ? How are you wrong ?
>
> (okay, it's only the name which is wrong; it's DECIKELVIN_TO_MILLICELSIUS)
>
> Rene.
>

yep, I was confused by these names too ;)

		- Cyrill -

  reply	other threads:[~2008-04-19  6:17 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 15:37 Linux 2.6.25 Matthew
2008-04-18 15:43 ` Linus Torvalds
2008-04-18 16:02   ` Matthew
2008-04-18 19:38   ` Cyrill Gorcunov
2008-04-18 20:03     ` Cyrill Gorcunov
2008-04-19  3:05       ` Rene Herman
2008-04-19  3:20         ` Rene Herman
2008-04-19  6:17           ` Cyrill Gorcunov [this message]
2008-04-19 10:18             ` Matthew
2008-04-19 10:22               ` Matthew
2008-04-20 12:02                 ` Matthew
2008-04-24  3:36                   ` Len Brown
2008-04-18 16:24 ` Gene Heskett
2008-04-18 16:27 ` Gene Heskett
2008-04-18 19:18 ` Bart Van Assche
2008-04-18 20:24   ` Jiri Slaby
2008-04-18 20:50     ` Rudolf Marek
2008-04-19  1:51 ` Linux 2.6.25 (coretemp reads high temperatures) Len Brown
2008-04-21 16:10   ` Thomas Bächler
2008-04-21 16:28     ` Matthew
2008-04-21 17:07       ` Fwd: " Matthew
2008-04-22  9:26         ` Matthew
2008-04-23  8:43   ` Maxim Levitsky
2008-04-28 18:19     ` Kasper Sandberg
2008-04-29 13:07       ` Thomas Renninger
2008-04-29 15:08         ` Jean Delvare
2008-04-29 22:14           ` Rudolf Marek
2008-04-29 22:58             ` Matthew
2008-04-30  6:10               ` Jean Delvare
2008-04-30 14:46                 ` Henrique de Moraes Holschuh
2008-04-30 14:50                   ` Rudolf Marek
2008-04-30 15:18                     ` Jean Delvare
2008-05-02 20:35                   ` Pavel Machek
2008-04-30  0:11             ` Kasper Sandberg
2008-04-30  6:20               ` Jean Delvare
2008-04-30 14:51                 ` Henrique de Moraes Holschuh
2008-04-30 15:28                   ` Jean Delvare
2008-05-02 20:36                   ` Pavel Machek
2008-05-04 17:42                     ` Henrique de Moraes Holschuh
2008-05-05 13:45                       ` Pavel Machek
2008-05-02 20:35             ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2008-04-17  3:32 Linux 2.6.25 Linus Torvalds
2008-04-17  4:22 ` david
2008-04-17 18:56   ` Rafael J. Wysocki

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=20080419061701.GA7688@cvg \
    --to=gorcunov@gmail.com \
    --cc=jackdachef@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@keyaccess.nl \
    --cc=torvalds@linux-foundation.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).