<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers, branch v2.6.14.3</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers?h=v2.6.14.3</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers?h=v2.6.14.3'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2005-11-24T22:10:12Z</updated>
<entry>
<title>[PATCH] hwmon: Fix missing it87 fan div init</title>
<updated>2005-11-24T22:10:12Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2005-11-21T18:22:16Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4e980ac962bc77d292ad4039631553dd2a88d47f'/>
<id>urn:sha1:4e980ac962bc77d292ad4039631553dd2a88d47f</id>
<content type='text'>
Fix a bug where setting the low fan speed limits will not work if no
data was ever read through the sysfs interface and the fan clock
dividers have not been explicitely set yet either. The reason is that
data-&gt;fan_div[nr] may currently be used before it is initialized from
the chip register values. The fix is to explicitely initialize
data-&gt;fan_div[nr] before using it.

Bug reported, and fix tested, by Nicolas Mailhot.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] hwmon: Fix lm78 VID conversion</title>
<updated>2005-11-24T22:10:12Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2005-11-14T22:11:45Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ce79890ea55a84b3600bbee421be78117c2532bb'/>
<id>urn:sha1:ce79890ea55a84b3600bbee421be78117c2532bb</id>
<content type='text'>
Fix the lm78 VID reading, which I accidentally broke while making
this driver use the common vid_from_reg function rather than
reimplementing its own in 2.6.14-rc1.

I'm not proud of it, trust me.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] hwmon: Fix missing boundary check when setting W83627THF in0 limits</title>
<updated>2005-11-24T22:10:12Z</updated>
<author>
<name>Yuan Mu</name>
<email>Ymu@winbond.com.tw</email>
</author>
<published>2005-11-14T22:08:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=30b2b8ee1866188c1f86aefe7dedca4b9681772f'/>
<id>urn:sha1:30b2b8ee1866188c1f86aefe7dedca4b9681772f</id>
<content type='text'>
Add SENSORS_LIMIT in store VCore limit functions. This fixes a potential
u8 overflow on out-of-range user input.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] drivers/isdn/hardware/eicon/os_4bri.c: correct the xdiLoadFile() signature</title>
<updated>2005-11-24T22:10:12Z</updated>
<author>
<name>Adrian Bunk</name>
<email>bunk@stusta.de</email>
</author>
<published>2005-11-19T07:58:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=fb69773ded08e5b679db97a84aa7ce371c5f6208'/>
<id>urn:sha1:fb69773ded08e5b679db97a84aa7ce371c5f6208</id>
<content type='text'>
It's not good if caller and callee disagree regarding the type of the
arguments.

In this case, this could cause problems on 64bit architectures.

Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
Signed-off-by: Armin Schindler &lt;armin@melware.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] Generic HDLC WAN drivers - disable netif_carrier_off()</title>
<updated>2005-11-24T22:10:08Z</updated>
<author>
<name>Krzysztof Halasa</name>
<email>khc@pm.waw.pl</email>
</author>
<published>2005-11-11T00:54:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e193ed753d6f1301a06b797e512e01e3c569fec8'/>
<id>urn:sha1:e193ed753d6f1301a06b797e512e01e3c569fec8</id>
<content type='text'>
As we are currently unable to fix the problem with carrier and protocol
state signaling in net core I've to disable netif_carrier_off() calls
used by WAN protocol drivers. The attached patch should make them
working again.

The remaining netif_carrier_*() calls in hdlc_fr.c are fine as they
don't touch the physical device.

Signed-off-by: Krzysztof Halasa &lt;khc@pm.waw.pl&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] packet writing oops fix</title>
<updated>2005-11-24T22:10:07Z</updated>
<author>
<name>Peter Osterlund</name>
<email>petero2@telia.com</email>
</author>
<published>2005-11-14T00:06:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9761be89f5a057bf2bae57ca98990f89ad5edbe2'/>
<id>urn:sha1:9761be89f5a057bf2bae57ca98990f89ad5edbe2</id>
<content type='text'>
There is an old bug in the pkt_count_states() function that causes stack
corruption.  When compiling with gcc 3.x or 2.x it is harmless, but gcc 4
allocates local variables differently, which makes the bug visible.

Signed-off-by: Peter Osterlund &lt;petero2@telia.com&gt;
Cc: &lt;stable@kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix soft lockup with ALSA rtc-timer</title>
<updated>2005-11-24T22:10:07Z</updated>
<author>
<name>Takashi Iwai</name>
<email>tiwai@suse.de</email>
</author>
<published>2005-11-11T18:47:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d8122124872548142e3df57d274444f484f318a2'/>
<id>urn:sha1:d8122124872548142e3df57d274444f484f318a2</id>
<content type='text'>
Fixed the soft lockup of ALSA rtc-timer due to the wrong irq
handling in rtc_control().  The call of rtc_control() can be atomic.

Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] airo.c/airo_cs.c: correct prototypes</title>
<updated>2005-11-11T05:18:55Z</updated>
<author>
<name>Adrian Bunk</name>
<email>bunk@stusta.de</email>
</author>
<published>2005-11-09T18:22:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f6e896dc60c84b5c5fb800c8e714b14f6e43668d'/>
<id>urn:sha1:f6e896dc60c84b5c5fb800c8e714b14f6e43668d</id>
<content type='text'>
This patch creates a file airo.h containing prototypes of the global
functions in airo.c used by airo_cs.c .

If you got strange problems with either airo_cs devices or in any other
completely unrelated part of the kernel shortly or long after a airo_cs
device was detected by the kernel, this might have been caused by the
fact that caller and callee disagreed regarding the size of the first
argument to init_airo_card()...

Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] USB: always export interface information for modalias</title>
<updated>2005-11-11T05:18:55Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@suse.de</email>
</author>
<published>2005-11-09T18:22:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0b7a194cceea9ac1c2cf9de3cffc5b735773c451'/>
<id>urn:sha1:0b7a194cceea9ac1c2cf9de3cffc5b735773c451</id>
<content type='text'>
This fixes a problem with some cdc acm devices that were not getting
automatically loaded as the module alias was not being reported
properly.

This check was for back in the days when we only reported hotplug events
for the main usb device, not the interfaces.  We should always give the
interface information for MODALIAS/modalias as it can be needed.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Oops on suspend after on-the-fly switch to anticipatory i/o scheduler - PowerBook5, 4</title>
<updated>2005-11-11T05:18:54Z</updated>
<author>
<name>Jens Axboe</name>
<email>axboe@suse.de</email>
</author>
<published>2005-11-09T18:22:08Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d47698c7ff2a71160e1095161e841af1ddd9fe8b'/>
<id>urn:sha1:d47698c7ff2a71160e1095161e841af1ddd9fe8b</id>
<content type='text'>
Paul Collins wrote:
&gt;I boot with elevator=cfq (wanted to try the ionice stuff, never got
&gt;around to it).  Having decided to go back to the anticipatory
&gt;scheduler, I did the following:
&gt;
&gt;# echo anticipatory &gt; /sys/block/hda/queue/scheduler
&gt;# echo anticipatory &gt; /sys/block/hdc/queue/scheduler
&gt;
&gt;A while later I did 'sudo snooze', which produced the Oops below.
&gt;
&gt;Booting with elevator=as and then changing to cfq, sleep works fine.
&gt;But if I resume and change back to anticipatory I get a similar Oops
&gt;on the next 'sudo snooze'.
&gt;
&gt;
&gt;  Oops: kernel access of bad area, sig: 11 [#1]
&gt;  NIP: C01E1948 LR: C01D6A60 SP: EFBC5C20 REGS: efbc5b70 TRAP: 0300
&gt;Not tainted
&gt;  MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
&gt;  DAR: 00000020, DSISR: 40000000
&gt;  TASK = efb012c0[1213] 'pmud' THREAD: efbc4000
&gt;  Last syscall: 54   GPR00: 00080000 EFBC5C20 EFB012C0 EFE9E044
&gt;EFBC5CE8 00000002 00000000 C03B0000   GPR08: C046E5D8 00000000
&gt;C03B47C8 E6A58360 22042422 1001E4DC 10010000 10000000   GPR16:
&gt;10000000 10000000 10000000 7FE4EB40 10000000 10000000 10010000
&gt;C0400000   GPR24: C0380000 00000002 00000002 C046E0C0 00000000
&gt;00000002 00000000 EFBC5CE8   NIP [c01e1948] as_insert_request+0xa8/0x6b0
&gt;  LR [c01d6a60] __elv_add_request+0xa0/0x100
&gt;  Call trace:
&gt;   [c01d6a60] __elv_add_request+0xa0/0x100
&gt;   [c01ffb84] ide_do_drive_cmd+0xb4/0x190
&gt;   [c01fc1c0] generic_ide_suspend+0x80/0xa0
&gt;   [c01d4574] suspend_device+0x104/0x160
&gt;   [c01d47c0] device_suspend+0x120/0x330
&gt;   [c03f3b50] pmac_suspend_devices+0x50/0x1b0
&gt;   [c03f4294] pmu_ioctl+0x344/0x9b0
&gt;   [c0082aa4] do_ioctl+0x84/0x90
&gt;   [c0082b3c] vfs_ioctl+0x8c/0x460
&gt;   [c0082f50] sys_ioctl+0x40/0x80
&gt;   [c0004850] ret_from_syscall+0x0/0x4c

Don't clear -&gt;elevator_data on exit, if we are switching queues we are
overwriting the data of the new io scheduler.

Signed-off-by: Jens Axboe &lt;axboe@suse.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
</feed>
