<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors">
    <title>gmane.linux.drivers.sensors</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32543"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32542"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32541"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32540"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32539"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32538"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32537"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32536"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32535"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32534"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32533"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32532"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32531"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32530"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32529"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32528"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32527"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32526"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32525"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.sensors/32524"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32543">
    <title>pwmconfig acpi vs. hwmon, no fancontrol config</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32543</link>
    <description>&lt;pre&gt;The pwmconfig doesn't find the fan device but I can echo commands
to get the cpu fan to stop and start.  Haven't been able to do anything
with the chassis fan.

When I run pwmconfig it reports "no correlation" and I don't get
a fancontrol cfg file. I edited the pwmconfig to look at acpi first
instead of hwmon and there's no difference.

The w83l786g seems to have some kind of watchdog on it as well but
not sure what this means. But while I was trying to sort out the fans
the system crashed. I found that the watchdog detected something and
decided to reboot. I am going to build a 3.9.4 kernel for the watchdog
issue but I don't think it's related to fan problems.


_______________________________________________
lm-sensors mailing list
lm-sensors-GZX6beZjE8VD60Wz+7aTrA&amp;lt; at &amp;gt;public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

&lt;/pre&gt;</description>
    <dc:creator>rh</dc:creator>
    <dc:date>2013-05-25T23:39:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32542">
    <title>Самое выигрышное предложение ради гостей нашего сайта</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32542</link>
    <description>&lt;pre&gt;Самое практичное предложение для экскурсантов нашего сайта http://goo.gl/yZV3s?/SIWfCA

_______________________________________________
lm-sensors mailing list
lm-sensors&amp;lt; at &amp;gt;lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors&lt;/pre&gt;</description>
    <dc:creator>agpdljb8t2uuk</dc:creator>
    <dc:date>2013-05-25T09:04:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32541">
    <title>Re: lm-sensors help question</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32541</link>
    <description>&lt;pre&gt;
The thermal margin is comfortable, your CPU cooling is more than
adequate :)

Jean

&lt;/pre&gt;</description>
    <dc:creator>Jean Delvare</dc:creator>
    <dc:date>2013-05-25T07:18:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32540">
    <title>Re: lm-sensors help question</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32540</link>
    <description>&lt;pre&gt;
Thanks again for the useful information.  Looking through dmesg you are 
probably right since I am getting an ACPI error shortly after the it87 
driver loads, as shown below:

[   13.891413] it87: Found IT8718F chip at 0xe80, revision 5
[   13.891423] it87: VID is disabled (pins used for GPIO)
[   13.891459] ACPI Warning: 0x0000000000000e85-0x0000000000000e86 
SystemIO conflicts with Region \SENP 1 (20120320/utaddress-251)
[   13.891464] ACPI: If an ACPI driver is available for this device, you 
should use it instead of the native driver
[   13.891507] fglrx: module license 'Proprietary. (C) 2002 - ATI 
Technologies, Starnberg, GERMANY' taints kernel.
[   13.891513] Disabling lock debugging due to kernel taint
[   13.892406] ACPI Warning: 0x0000000000000b00-0x0000000000000b07 
SystemIO conflicts with Region \SOR1 1 (20120320/utaddress-251)
[   13.892416] ACPI: If an ACPI driver is available for this device, you 
should use it instead of the native driver

I updated to Ubuntu 12.04 64 bit versus 32 bit but t&lt;/pre&gt;</description>
    <dc:creator>Bruce Kettle</dc:creator>
    <dc:date>2013-05-25T01:19:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32539">
    <title>Re: ITE IT8518E supported in coreboot, helpful?</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32539</link>
    <description>&lt;pre&gt;
I may be missing something, but my understanding is that the chip
has an embedded microcontroller (EC) which handles the actual fan
control. While the chip data sheet describes the hardware accessible
to the EC, and the API between CPU and EC, it does not describe
the logical interface between the two. Problem is that this
interface is not well defined and depends on the microcode
running on the EC.

The file referenced above seems to provide that information for the
specific board and for the microcode running on the EC in that board
(which appears to be the referenced 'quanta' firmware). That does
not mean, however, that it would be the same for other boards,
including yours.

A second potential problem is that the ACPI data provided above suggests
that the EC may be controlled through ACPI, which means that ACPI most
likely reserves the memory space needed to access the controller.
If this is the case in your system, which is quite likely, your best
option would be an ACPI driver.

Thanks,
Guenter


____&lt;/pre&gt;</description>
    <dc:creator>Guenter Roeck</dc:creator>
    <dc:date>2013-05-24T17:34:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32538">
    <title>Re: W83L786G not detected on vx800</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32538</link>
    <description>&lt;pre&gt;On Fri, 24 May 2013 08:59:27 +0200
Jean Delvare &amp;lt;khali-PUYAD+kWke1g9hUCZPvPmw&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


I only know that my fans are  running all the time and lmsensors was
mentioned everywhere I looked.


sensors-detect


That returns cpu temp and data from the w83l786! (don't have it
to cut-n-paste)


They do look close enough after reading the datasheet for each. 


I tried this and sensors-detect produces the same output.
It seems I don't need to rely on sensors-detect though and
need to find out why pwmconfig cannot control the fans.

But it's another guess. I did see that in the 3.9.2 kernel there's
a separate flag for PWM that I had never noticed before. I think
it's new. I checked the box for that.

I just want to have fan control and it seems all the pieces are there
but something's missing.  It could be PEBKAC but I've looked at a
lot of stuff....the vx800 spec, the W83l786NG,NR,G,R datasheets,
linux/Documentation/hwmon, thermal, etc., etc.

Thanks for lm-sensors! And thanks for taking the time to&lt;/pre&gt;</description>
    <dc:creator>rh</dc:creator>
    <dc:date>2013-05-24T15:28:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32537">
    <title>Re: lm-sensors help question</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32537</link>
    <description>&lt;pre&gt;
And? PCI is a system bus. The value is retrieved over the PCI bus.
That's all it means, really.


Did you actually try loading the it87 driver? Did it work? If not, you
may be another victim of ACPI:
http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31

&lt;/pre&gt;</description>
    <dc:creator>Jean Delvare</dc:creator>
    <dc:date>2013-05-24T15:26:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32536">
    <title>Re: [PATCH v3] hwmon (ds1621): Remove detectionfunction</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32536</link>
    <description>&lt;pre&gt;Applied to -next.

Thanks a lot to both of you!

Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors&amp;lt; at &amp;gt;lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

&lt;/pre&gt;</description>
    <dc:creator>Guenter Roeck</dc:creator>
    <dc:date>2013-05-24T14:56:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32535">
    <title>Re: sensord systemd unit</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32535</link>
    <description>&lt;pre&gt;Hi Nikola,

Sorry for the late reply :(

On Mon, 13 Feb 2012 14:37:22 +0100, Nikola Pajkovsky wrote:

I added:
After=syslog.target


I removed the "-", as the environment file is mandatory, otherwise the
ExecStart below will fail, right?


Applied, thanks!

&lt;/pre&gt;</description>
    <dc:creator>Jean Delvare</dc:creator>
    <dc:date>2013-05-24T12:57:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32534">
    <title>Re: lm-sensors help question</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32534</link>
    <description>&lt;pre&gt;Thank you for responding.  So this reading is actually the CPU temp?  
It's the only k10temp reading returned but it's labelled for pci.

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +23.5°C  (high = +70.0°C)
                         (crit = +90.0°C, hyst = +88.0°C)

Here is output from sensors-detect.


bruce&amp;lt; at &amp;gt;bruce-A780L3G:~$ sudo sensors-detect
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# System: BIOSTAR Group A780L3G

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...            &lt;/pre&gt;</description>
    <dc:creator>Bruce Kettle</dc:creator>
    <dc:date>2013-05-24T12:36:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32533">
    <title>ITE IT8518E supported in coreboot, helpful?</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32533</link>
    <description>&lt;pre&gt;This controller is giving people some trouble, as it is shipped in more 
and more laptops [1] and the fans can become quite annoying in these 
systems.

In the past it was said that the main problem was the lack of a 
datasheet from ITE [2]. Recently there has been progress from the 
coreboot projects getting the info for quanta firmware on IT8518 [3]. 
Can this particular file help with the lack of specs or it depends on 
other factors?
http://review.coreboot.org/gitweb?p=coreboot.git;a=blob;f=src/ec/quanta/it8518/acpi/ec.asl;h=7549fa283da69b9b1fca8589b1fc7f59fd30f7a4;hb=7e568559634199668859b7c662aea7f6b41f3920

In my particular case, I have a noisy clevo p150em. I can help providing 
testing and perhaps developing - just looking at the code of other 
modules, it87, it seems to me I could give a hand beyond testing.

Thanks

[1] https://bbs.archlinux.org/viewtopic.php?id=154462
      http://forums.debian.net/viewtopic.php?f=7&amp;amp;t=76146
http://forums.opensuse.org/english/get-technical-help-here/laptop/486412-c&lt;/pre&gt;</description>
    <dc:creator>Santi Villalba</dc:creator>
    <dc:date>2013-05-24T09:47:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32532">
    <title>Re: [PATCH v3] hwmon (ds1621): Remove detection function</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32532</link>
    <description>&lt;pre&gt;Hi Robert,

On Thu, 23 May 2013 09:22:22 -0700, Robert Coulson wrote:

Thanks for the update, looks good to me.

Acked-by: Jean Delvare &amp;lt;khali&amp;lt; at &amp;gt;linux-fr.org&amp;gt;

Guenter, please pick and apply.

&lt;/pre&gt;</description>
    <dc:creator>Jean Delvare</dc:creator>
    <dc:date>2013-05-24T07:05:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32531">
    <title>Re: lm-sensors help question</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32531</link>
    <description>&lt;pre&gt;Hi Bruce,

On Thu, 23 May 2013 21:40:27 -0600, Bruce Kettle wrote:

k10temp is the CPU core temp. The value might be different from what you
expect because these embedded sensors have very poor accuracy in low
temperature ranges. What the above value really means is that your CPU
is properly cooled and you do not have to worry about overheating
(unless the value gets close to 70°C under heavy load.)


What "chipset" are you talking about, please?


What monitoring chip do these programs report? I can't help you further
without the complete output of a recent version of sensors-detect (for
example http://dl.lm-sensors.org/lm-sensors/files/sensors-detect) on
your system.

&lt;/pre&gt;</description>
    <dc:creator>Jean Delvare</dc:creator>
    <dc:date>2013-05-24T07:03:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32530">
    <title>Re: W83L786G not detected on vx800</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32530</link>
    <description>&lt;pre&gt;Hi Richard,

On Fri, 24 May 2013 03:21:29 -0700, rh wrote:

Running sensors-detect on a monolithic kernel is rather pointless. The
whole purpose of sensors-detect is to tell you which kernel modules
should be loaded. If you built a monolithic kernel you must already
know that.


"lmsensors" is a set of tools. Which tool(s) are you claiming can't see
the device? sensors-detect? sensors? Both? Something else?

What does "sensors" return?


It is there indeed.


Should't matter, while the chips aren't 100% compatible they have the
same chip ID so the same driver supports both.


This is your W83L786G chip. sensors-detect would tell you if the driver
was built as a module rather than embedded in the kernel.

I have improved sensors-detect so that it can handle monolithic kernels
better. Please give it a try and report the output:
  http://khali.linux-fr.org/devel/lm-sensors/sensors-detect

&lt;/pre&gt;</description>
    <dc:creator>Jean Delvare</dc:creator>
    <dc:date>2013-05-24T06:59:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32529">
    <title>lm-sensors help question</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32529</link>
    <description>&lt;pre&gt;Hi I have a Biostar a780l3g motherboard with a Phenom II 840 processor.  
I have Ubuntu 12.04 32-bit installed and current patches (kernel 
3.5.0-30-generic).  I installed lm-sensors and ran sensors-detect, it 
properly detected the k10 sensors.  But when I run sensors the output is 
as follows:

bruce&amp;lt; at &amp;gt;bruce-A780L3G:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +32.0°C  (crit = +127.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +23.5°C  (high = +70.0°C)
                        (crit = +90.0°C, hyst = +88.0°C)

I was hoping to be able to read core temps, but I don't think either of 
these are that.

It does not appear that Biostar provides Linux chipset drivers, although 
your FAQ indicates this should be supported in this version of the 
kernel.  Is there something I am doing wrong or is the board just not 
supported?  The sensors did work in Windows 7 in a variety of programs, 
so I don't think there is a hardware issue.

Thanks




_____________________________________&lt;/pre&gt;</description>
    <dc:creator>Bruce Kettle</dc:creator>
    <dc:date>2013-05-24T03:40:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32528">
    <title>Доброго Вам дня</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32528</link>
    <description>&lt;pre&gt;Самое хлебное предложение для посетителей нашего сайта http://goo.gl/cZgzh?/CahE 
_______________________________________________
lm-sensors mailing list
lm-sensors&amp;lt; at &amp;gt;lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors&lt;/pre&gt;</description>
    <dc:creator>tamazi.burduli</dc:creator>
    <dc:date>2013-05-24T00:23:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32527">
    <title>W83L786G not detected on vx800</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32527</link>
    <description>&lt;pre&gt;Hello,

On the MB there is a winbond W83L786G but it is not detected
by sensors-detect.  The  kernel is monolithic (i.e. no modules)
and it is linux3.9.2.

It seems that lmsensors is unable to see this device but it is there.

cat /sys/class/hwmon/hwmon1/device/name
w83l786ng

As I said the actual device is a w83l786g

Tips/pointers/suggestions much appreciated as the fans are
running at ~80% all the time.



# sensors-detect revision 6085 (2012-10-30 18:18:45 +0100)
# System: VIA Technologies Ltd. VX800 [1.0]

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): 
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 I&lt;/pre&gt;</description>
    <dc:creator>rh</dc:creator>
    <dc:date>2013-05-24T10:21:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32526">
    <title>[PATCH v3] hwmon (ds1621): Remove detection function</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32526</link>
    <description>&lt;pre&gt;Due to a lack of device and vendor identification registers, the
Dallas/Maxim DS16xx devices cannot be uniquely detected, sometimes
resulting in false positives. Therefore, the detection function is
being removed in favor of explicit device instantiation.

Signed-off-by: Robert Coulson &amp;lt;rob.coulson&amp;lt; at &amp;gt;gmail.com&amp;gt;
---
 Documentation/hwmon/ds1621 |   25 +++++++++++------------
 drivers/hwmon/ds1621.c     |   48 --------------------------------------------
 2 files changed, 12 insertions(+), 61 deletions(-)

v2:
- removed detect function references in ds1621 documentation
- replaced deprecated with removed and fixed a spelling error
v3:
- removed scanned addresses info, tables, and list

diff --git a/Documentation/hwmon/ds1621 b/Documentation/hwmon/ds1621
index 140eab5..2022379 100644
--- a/Documentation/hwmon/ds1621
+++ b/Documentation/hwmon/ds1621
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -4,24 +4,22 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; Kernel driver ds1621
 Supported chips:
   * Dallas Semiconductor &amp;amp; Maxim Integrated DS1621
     Prefix: 'ds1621'
-    Addresses scanned: I2C 0x48 - 0x&lt;/pre&gt;</description>
    <dc:creator>Robert Coulson</dc:creator>
    <dc:date>2013-05-23T16:22:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32525">
    <title>Re: [PATCH] fancontrol: Fix handling of absolute paths in config</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32525</link>
    <description>&lt;pre&gt;
Thanks for testing. Patch committed and added to the list of
recommended patches.

&lt;/pre&gt;</description>
    <dc:creator>Jean Delvare</dc:creator>
    <dc:date>2013-05-23T14:18:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32524">
    <title>Re: [PATCH] fancontrol: Fix handling of absolute pathsin config</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32524</link>
    <description>&lt;pre&gt;

Yes. Just tested on my system and everything seems to run smoothly.

Thank you,

Marc

_______________________________________________
lm-sensors mailing list
lm-sensors&amp;lt; at &amp;gt;lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

&lt;/pre&gt;</description>
    <dc:creator>Marc Ferland</dc:creator>
    <dc:date>2013-05-23T13:42:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.sensors/32523">
    <title>Re: sensors-detect:: Drop detection of DS1621-likechips</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.sensors/32523</link>
    <description>&lt;pre&gt;

Good morning Jean,

you are correct and I apologize for the noise; i was not looking at the
master branch.

Rob.

_______________________________________________
lm-sensors mailing list
lm-sensors&amp;lt; at &amp;gt;lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors&lt;/pre&gt;</description>
    <dc:creator>Robert Coulson</dc:creator>
    <dc:date>2013-05-22T15:43:07</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.drivers.sensors">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.drivers.sensors</link>
  </textinput>
</rdf:RDF>
