<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers, branch v2.6.32.22</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers?h=v2.6.32.22</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers?h=v2.6.32.22'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2010-09-20T20:18:14Z</updated>
<entry>
<title>drm: Only decouple the old_fb from the crtc is we call mode_set*</title>
<updated>2010-09-20T20:18:14Z</updated>
<author>
<name>Chris Wilson</name>
<email>chris@chris-wilson.co.uk</email>
</author>
<published>2010-09-09T08:41:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6185dfa6d0aafb67732a1299867c72c56d6f69f3'/>
<id>urn:sha1:6185dfa6d0aafb67732a1299867c72c56d6f69f3</id>
<content type='text'>
commit 356ad3cd616185631235ffb48b3efbf39f9923b3 upstream.

Otherwise when disabling the output we switch to the new fb (which is
likely NULL) and skip the call to mode_set -- leaking driver private
state on the old_fb.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=29857
Reported-by: Sitsofe Wheeler &lt;sitsofe@yahoo.com&gt;
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Cc: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/i915: Prevent double dpms on</title>
<updated>2010-09-20T20:18:14Z</updated>
<author>
<name>Chris Wilson</name>
<email>chris@chris-wilson.co.uk</email>
</author>
<published>2010-09-06T15:17:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=adae873370266265202de840d19650a0a8289cd1'/>
<id>urn:sha1:adae873370266265202de840d19650a0a8289cd1</id>
<content type='text'>
commit 032d2a0d068b0368296a56469761394ef03207c3 upstream.

Arguably this is a bug in drm-core in that we should not be called twice
in succession with DPMS_ON, however this is still occuring and we see
FDI link training failures on the second call leading to the occassional
blank display. For the time being ignore the repeated call.

Original patch by Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>i915_gem: return -EFAULT if copy_to_user fails</title>
<updated>2010-09-20T20:18:14Z</updated>
<author>
<name>Dan Carpenter</name>
<email>error27@gmail.com</email>
</author>
<published>2010-06-23T17:03:01Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=079908f18d73154f76b8abb656d63bfeda0e201f'/>
<id>urn:sha1:079908f18d73154f76b8abb656d63bfeda0e201f</id>
<content type='text'>
commit c877cdce93a44eea96f6cf7fc04be7d0372db2be upstream.

copy_to_user() returns the number of bytes remaining to be copied and
I'm pretty sure we want to return a negative error code here.

Signed-off-by: Dan Carpenter &lt;error27@gmail.com&gt;
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>i915: return -EFAULT if copy_to_user fails</title>
<updated>2010-09-20T20:18:14Z</updated>
<author>
<name>Dan Carpenter</name>
<email>error27@gmail.com</email>
</author>
<published>2010-06-19T13:12:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9cd74cb5174c58dd7165f8cd10897bd775a9a777'/>
<id>urn:sha1:9cd74cb5174c58dd7165f8cd10897bd775a9a777</id>
<content type='text'>
commit 9927a403ca8c97798129953fa9cbb5dc259c7cb9 upstream.

copy_to_user returns the number of bytes remaining to be copied, but we
want to return a negative error code here.  These are returned to
userspace.

Signed-off-by: Dan Carpenter &lt;error27@gmail.com&gt;
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>apm_power: Add missing break statement</title>
<updated>2010-09-20T20:18:13Z</updated>
<author>
<name>Anton Vorontsov</name>
<email>cbouatmailru@gmail.com</email>
</author>
<published>2010-09-07T20:10:26Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=198aa4b040aa00b4c9de5314da2338ff20ab1f73'/>
<id>urn:sha1:198aa4b040aa00b4c9de5314da2338ff20ab1f73</id>
<content type='text'>
commit 1d220334d6a8a711149234dc5f98d34ae02226b8 upstream.

The missing break statement causes wrong capacity calculation for
batteries that report energy.

Reported-by: d binderman &lt;dcb314@hotmail.com&gt;
Signed-off-by: Anton Vorontsov &lt;cbouatmailru@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>hwmon: (f75375s) Do not overwrite values read from registers</title>
<updated>2010-09-20T20:18:13Z</updated>
<author>
<name>Guillem Jover</name>
<email>guillem@hadrons.org</email>
</author>
<published>2010-09-17T15:24:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ebd5849e44b2a3fe939d9b5b36270ae6f8b727f9'/>
<id>urn:sha1:ebd5849e44b2a3fe939d9b5b36270ae6f8b727f9</id>
<content type='text'>
commit c3b327d60bbba3f5ff8fd87d1efc0e95eb6c121b upstream.

All bits in the values read from registers to be used for the next
write were getting overwritten, avoid doing so to not mess with the
current configuration.

Signed-off-by: Guillem Jover &lt;guillem@hadrons.org&gt;
Cc: Riku Voipio &lt;riku.voipio@iki.fi&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>hwmon: (f75375s) Shift control mode to the correct bit position</title>
<updated>2010-09-20T20:18:13Z</updated>
<author>
<name>Guillem Jover</name>
<email>guillem@hadrons.org</email>
</author>
<published>2010-09-17T15:24:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2e999ac7a157b6fddb9bd5db8aff9188a9b458bb'/>
<id>urn:sha1:2e999ac7a157b6fddb9bd5db8aff9188a9b458bb</id>
<content type='text'>
commit 96f3640894012be7dd15a384566bfdc18297bc6c upstream.

The spec notes that fan0 and fan1 control mode bits are located in bits
7-6 and 5-4 respectively, but the FAN_CTRL_MODE macro was making the
bits shift by 5 instead of by 4.

Signed-off-by: Guillem Jover &lt;guillem@hadrons.org&gt;
Cc: Riku Voipio &lt;riku.voipio@iki.fi&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ath5k: check return value of ieee80211_get_tx_rate</title>
<updated>2010-09-20T20:17:55Z</updated>
<author>
<name>John W. Linville</name>
<email>linville@tuxdriver.com</email>
</author>
<published>2010-08-24T19:27:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=34cee821ec2b89a613947b72eec8f31305c58a93'/>
<id>urn:sha1:34cee821ec2b89a613947b72eec8f31305c58a93</id>
<content type='text'>
commit d8e1ba76d619dbc0be8fbeee4e6c683b5c812d3a upstream.

This avoids a NULL pointer dereference as reported here:

	https://bugzilla.redhat.com/show_bug.cgi?id=625889

When the WARN condition is hit in ieee80211_get_tx_rate, it will return
NULL.  So, we need to check the return value and avoid dereferencing it
in that case.

Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Acked-by: Bob Copeland &lt;me@bobcopeland.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>p54: fix tx feedback status flag check</title>
<updated>2010-09-20T20:17:55Z</updated>
<author>
<name>Christian Lamparter</name>
<email>chunkeey@googlemail.com</email>
</author>
<published>2010-08-24T20:54:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8fdd6243c34ea97465f10be83384f7c9cafb17f5'/>
<id>urn:sha1:8fdd6243c34ea97465f10be83384f7c9cafb17f5</id>
<content type='text'>
commit f880c2050f30b23c9b6f80028c09f76e693bf309 upstream.

Michael reported that p54* never really entered power
save mode, even tough it was enabled.

It turned out that upon a power save mode change the
firmware will set a special flag onto the last outgoing
frame tx status (which in this case is almost always the
designated PSM nullfunc frame). This flag confused the
driver; It erroneously reported transmission failures
to the stack, which then generated the next nullfunc.
and so on...

Reported-by: Michael Buesch &lt;mb@bu3sch.de&gt;
Tested-by: Michael Buesch &lt;mb@bu3sch.de&gt;
Signed-off-by: Christian Lamparter &lt;chunkeey@googlemail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Input: i8042 - fix device removal on unload</title>
<updated>2010-09-20T20:17:54Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2010-09-01T00:27:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e3327857e9b33f2cb9921e469f9ea1806fdedc9b'/>
<id>urn:sha1:e3327857e9b33f2cb9921e469f9ea1806fdedc9b</id>
<content type='text'>
commit af045b86662f17bf130239a65995c61a34f00a6b upstream.

We need to call platform_device_unregister(i8042_platform_device)
before calling platform_driver_unregister() because i8042_remove()
resets i8042_platform_device to NULL. This leaves the platform device
instance behind and prevents driver reload.

Fixes https://bugzilla.kernel.org/show_bug.cgi?id=16613

Reported-by: Seryodkin Victor &lt;vvscore@gmail.com&gt;
Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
