<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers, branch v2.6.32.4</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers?h=v2.6.32.4</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers?h=v2.6.32.4'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2010-01-18T18:19:53Z</updated>
<entry>
<title>agp/intel-agp: Clear entire GTT on startup</title>
<updated>2010-01-18T18:19:53Z</updated>
<author>
<name>David Woodhouse</name>
<email>dwmw2@infradead.org</email>
</author>
<published>2009-12-02T11:00:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5877960869333e42ebeb733e8d9d5630ff96d350'/>
<id>urn:sha1:5877960869333e42ebeb733e8d9d5630ff96d350</id>
<content type='text'>
commit fc61901373987ad61851ed001fe971f3ee8d96a3 upstream.

Some BIOSes fail to initialise the GTT, which will cause DMA faults when
the IOMMU is enabled. We need to clear the whole thing to point at the
scratch page, not just the part that Linux is going to use.

Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
[anholt: Note that this may also help with stability in the presence of
driver bugs, by not drawing to memory we don't own]
Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Cc: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;
Cc: Ben Hutchings &lt;ben@decadent.org.uk&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>libertas: Remove carrier signaling from the scan code</title>
<updated>2010-01-18T18:19:49Z</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2009-12-18T10:36:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=904e3733fd1c50e81f4726f56759343207874a95'/>
<id>urn:sha1:904e3733fd1c50e81f4726f56759343207874a95</id>
<content type='text'>
commit 659c8e5243caf14564155ad8421404f044dd8031 upstream.

There is no reason to signal a carrier off when doing a 802.11 scan.

Cc: Holger Schurig &lt;holgerschurig@gmail.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
Acked-by: Dan Williams &lt;dcbw@redhat.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>drm/i915: remove render reclock support</title>
<updated>2010-01-18T18:19:48Z</updated>
<author>
<name>Jesse Barnes</name>
<email>jbarnes@virtuousgeek.org</email>
</author>
<published>2009-12-17T19:11:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b9945e752afed38518d7041ae00dea25f6272a34'/>
<id>urn:sha1:b9945e752afed38518d7041ae00dea25f6272a34</id>
<content type='text'>
commit cda9d05c499093c67b4a376a15009923acc2127a upstream.

This code generally fails to adjust the render clock, and when it does,
it conflicts with some other register settings and can cause problems.

So remove this code altogether.  I'm reworking it now to do the right
thing, but the only bit it will share is the VBT check for whether
reclocking is supported, so I'm leaving that bit.

Reverts most of 652c393a3368af84359da37c45afc35a91144960 ("add dynamic
clock frequency control"), though for many the regressions showed up
in the later 181a5336d6cc836f05507410d66988c483ad0154 ("Fix render
reclock availability detection").

Signed-off-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>iwl: off by one bug</title>
<updated>2010-01-18T18:19:46Z</updated>
<author>
<name>Dan Carpenter</name>
<email>error27@gmail.com</email>
</author>
<published>2010-01-03T09:19:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0ea5505e18a1cb8eebf3384f825840897894ceda'/>
<id>urn:sha1:0ea5505e18a1cb8eebf3384f825840897894ceda</id>
<content type='text'>
commit 8a9ac160e844c7ce8074f6aa531feefb4acdee7c upstream.

tid is used as an array offset.
	agg = &amp;priv-&gt;stations[sta_id].tid[tid].agg;
	iwl4965_tx_status_reply_tx(priv, agg, tx_resp, txq_id, index);

It should be limitted to MAX_TID_COUNT - 1;
        struct iwl_tid_data tid[MAX_TID_COUNT];

regards,
dan carpenter

Signed-off-by: Dan Carpenter &lt;error27@gmail.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>ath5k: Fix eeprom checksum check for custom sized eeproms</title>
<updated>2010-01-18T18:19:45Z</updated>
<author>
<name>Luis R. Rodriguez</name>
<email>lrodriguez@atheros.com</email>
</author>
<published>2010-01-04T15:40:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e6efac7b7c4ce45d40f5e07d3105e07704e95673'/>
<id>urn:sha1:e6efac7b7c4ce45d40f5e07d3105e07704e95673</id>
<content type='text'>
commit 359207c687cc8f4f9845c8dadd0d6dabad44e584 upstream.

Commit 8bf3d79bc401ca417ccf9fc076d3295d1a71dbf5 enabled EEPROM
checksum checks to avoid bogus bug reports but failed to address
updating the code to consider devices with custom EEPROM sizes.
Devices with custom sized EEPROMs have the upper limit size stuffed
in the EEPROM. Use this as the upper limit instead of the static
default size. In case of a checksum error also provide back the
max size and whether or not this was the default size or a custom
one. If the EEPROM is busted we add a failsafe check to ensure
we don't loop forever or try to read bogus areas of hardware.

This closes bug 14874

http://bugzilla.kernel.org/show_bug.cgi?id=14874

Cc: David Quan &lt;david.quan@atheros.com&gt;
Cc: Stephen Beahm &lt;stephenbeahm@comcast.net&gt;
Reported-by: Joshua Covington &lt;joshuacov@googlemail.com&gt;
Signed-off-by: Luis R. Rodriguez &lt;lrodriguez@atheros.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>iwlwifi: fix iwl_queue_used bug when read_ptr == write_ptr</title>
<updated>2010-01-18T18:19:44Z</updated>
<author>
<name>Zhu Yi</name>
<email>yi.zhu@intel.com</email>
</author>
<published>2010-01-08T18:04:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=fc95845f174a07d4200a30681067d22c9e34723c'/>
<id>urn:sha1:fc95845f174a07d4200a30681067d22c9e34723c</id>
<content type='text'>
commit c8106d7625a58ee4387cb2efe3e82320ad44b467 upstream.

When txq read_ptr equals to write_ptr, iwl_queue_used should
always return false. Because there is no used TFD in this case.

This is a complementary fix to the fix already included in commit "iwl3945:
fix panic in iwl3945 driver". Both fixes are needed to address the panic
below.

This problem was discussed on linux-wireless in
http://thread.gmane.org/gmane.linux.kernel.wireless.general/43568

&lt;1&gt;[ 7290.414172] IP: [&lt;ffffffffa0dd53a1&gt;] iwl3945_rx_reply_tx+0xc1/0x450 [iwl3945]
&lt;4&gt;[ 7290.414205] PGD 0
&lt;1&gt;[ 7290.414214] Thread overran stack, or stack corrupted
&lt;0&gt;[ 7290.414229] Oops: 0002 [#1] PREEMPT SMP
&lt;0&gt;[ 7290.414246] last sysfs file: /sys/devices/platform/coretemp.1/temp1_input
&lt;4&gt;[ 7290.414265] CPU 0
&lt;4&gt;[ 7290.414274] Modules linked in: af_packet nfsd usb_storage usb_libusual cpufreq_powersave exportfs cpufreq_conservative iwl3945 nfs cpufreq_userspace snd_hda_codec_realtek acpi_cpufreq uvcvideo lockd iwlcore snd_hda_intel joydev coretemp nfs_acl videodev snd_hda_codec mac80211 v4l1_compat snd_hwdep sbp2 v4l2_compat_ioctl32 uhci_hcd psmouse auth_rpcgss ohci1394 cfg80211 ehci_hcd video ieee1394 snd_pcm serio_raw battery ac nvidia(P) usbcore output sunrpc evdev lirc_ene0100 snd_page_alloc rfkill tg3 libphy fuse lzo lzo_decompress lzo_compress
&lt;6&gt;[ 7290.414486] Pid: 0, comm: swapper Tainted: P           2.6.32-rc8-wl #213 Aspire 5720
&lt;6&gt;[ 7290.414507] RIP: 0010:[&lt;ffffffffa0dd53a1&gt;]  [&lt;ffffffffa0dd53a1&gt;] iwl3945_rx_reply_tx+0xc1/0x450 [iwl3945]
&lt;6&gt;[ 7290.414541] RSP: 0018:ffff880002203d60  EFLAGS: 00010246
&lt;6&gt;[ 7290.414557] RAX: 000000000000004f RBX: ffff880064c11600 RCX: 0000000000000013
&lt;6&gt;[ 7290.414576] RDX: ffffffffa0ddcf20 RSI: ffff8800512b7008 RDI: 0000000000000038
&lt;6&gt;[ 7290.414596] RBP: ffff880002203dd0 R08: 0000000000000000 R09: 0000000000000100
&lt;6&gt;[ 7290.414616] R10: 0000000000000001 R11: 0000000000000000 R12: 00000000000000a0
&lt;6&gt;[ 7290.414635] R13: 0000000000000002 R14: 0000000000000013 R15: 0000000000020201
&lt;6&gt;[ 7290.414655] FS:  0000000000000000(0000) GS:ffff880002200000(0000) knlGS:0000000000000000
&lt;6&gt;[ 7290.414677] CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
&lt;6&gt;[ 7290.414693] CR2: 0000000000000041 CR3: 0000000001001000 CR4: 00000000000006f0
&lt;6&gt;[ 7290.414712] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
&lt;6&gt;[ 7290.414732] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
&lt;4&gt;[ 7290.414752] Process swapper (pid: 0, threadinfo ffffffff81524000, task ffffffff81528b60)
&lt;0&gt;[ 7290.414772] Stack:
&lt;4&gt;[ 7290.414780]  ffff880002203da0 0000000000000046 0000000000000000 0000000000000046
&lt;4&gt;[ 7290.414804] &lt;0&gt; 0000000000000282 0000000000000282 0000000000000282 ffff880064c12010
&lt;4&gt;[ 7290.414830] &lt;0&gt; ffff880002203db0 ffff880064c11600 ffff880064c12e50 ffff8800512b7000
&lt;0&gt;[ 7290.414858] Call Trace:
&lt;0&gt;[ 7290.414867]  &lt;IRQ&gt;
&lt;4&gt;[ 7290.414884]  [&lt;ffffffffa0dc8c47&gt;] iwl3945_irq_tasklet+0x657/0x1740 [iwl3945]
&lt;4&gt;[ 7290.414910]  [&lt;ffffffff8138fc60&gt;] ? _spin_unlock+0x30/0x60
&lt;4&gt;[ 7290.414931]  [&lt;ffffffff81049a21&gt;] tasklet_action+0x101/0x110
&lt;4&gt;[ 7290.414950]  [&lt;ffffffff8104a3d0&gt;] __do_softirq+0xc0/0x160
&lt;4&gt;[ 7290.414968]  [&lt;ffffffff8100d01c&gt;] call_softirq+0x1c/0x30
&lt;4&gt;[ 7290.414986]  [&lt;ffffffff8100eff5&gt;] do_softirq+0x75/0xb0
&lt;4&gt;[ 7290.415003]  [&lt;ffffffff81049ee5&gt;] irq_exit+0x95/0xa0
&lt;4&gt;[ 7290.415020]  [&lt;ffffffff8100e547&gt;] do_IRQ+0x77/0xf0
&lt;4&gt;[ 7290.415038]  [&lt;ffffffff8100c7d3&gt;] ret_from_intr+0x0/0xf
&lt;0&gt;[ 7290.415052]  &lt;EOI&gt;
&lt;4&gt;[ 7290.415067]  [&lt;ffffffff81234efa&gt;] ? acpi_idle_enter_bm+0x270/0x2a5
&lt;4&gt;[ 7290.415087]  [&lt;ffffffff81234f04&gt;] ? acpi_idle_enter_bm+0x27a/0x2a5
&lt;4&gt;[ 7290.415107]  [&lt;ffffffff81234efa&gt;] ? acpi_idle_enter_bm+0x270/0x2a5
&lt;4&gt;[ 7290.415130]  [&lt;ffffffff812c11f3&gt;] ? cpuidle_idle_call+0x93/0xf0
&lt;4&gt;[ 7290.415149]  [&lt;ffffffff8100b0d7&gt;] ? cpu_idle+0xa7/0x110
&lt;4&gt;[ 7290.415168]  [&lt;ffffffff8137b3d5&gt;] ? rest_init+0x75/0x80
&lt;4&gt;[ 7290.415187]  [&lt;ffffffff8158cd0a&gt;] ? start_kernel+0x3a7/0x3b3
&lt;4&gt;[ 7290.415206]  [&lt;ffffffff8158c315&gt;] ? x86_64_start_reservations+0x125/0x129
&lt;4&gt;[ 7290.415227]  [&lt;ffffffff8158c3fd&gt;] ? x86_64_start_kernel+0xe4/0xeb
&lt;0&gt;[ 7290.415243] Code: 00 41 39 ce 0f 8d e8 01 00 00 48 8b 47 40 48 63 d2 48 69 d2 98 00 00 00 4c 8b 04 02 48 c7 c2 20 cf dd a0 49 8d 78 38 49 8d 40 4f &lt;c6&gt; 47 09 00 c6 47 0c 00 c6 47 0f 00 c6 47 12 00 c6 47 15 00 49
&lt;1&gt;[ 7290.415382] RIP  [&lt;ffffffffa0dd53a1&gt;] iwl3945_rx_reply_tx+0xc1/0x450 [iwl3945]
&lt;4&gt;[ 7290.415410]  RSP &lt;ffff880002203d60&gt;
&lt;0&gt;[ 7290.415421] CR2: 0000000000000041
&lt;4&gt;[ 7290.415436] ---[ end trace ec46807277caa515 ]---
&lt;0&gt;[ 7290.415450] Kernel panic - not syncing: Fatal exception in interrupt
&lt;4&gt;[ 7290.415468] Pid: 0, comm: swapper Tainted: P      D    2.6.32-rc8-wl #213
&lt;4&gt;[ 7290.415486] Call Trace:
&lt;4&gt;[ 7290.415495]  &lt;IRQ&gt;  [&lt;ffffffff8138c040&gt;] panic+0x7d/0x13a
&lt;4&gt;[ 7290.415519]  [&lt;ffffffff8101071a&gt;] oops_end+0xda/0xe0
&lt;4&gt;[ 7290.415538]  [&lt;ffffffff8102e1ea&gt;] no_context+0xea/0x250
&lt;4&gt;[ 7290.415557]  [&lt;ffffffff81038991&gt;] ? select_task_rq_fair+0x511/0x780
&lt;4&gt;[ 7290.415578]  [&lt;ffffffff8102e475&gt;] __bad_area_nosemaphore+0x125/0x1e0
&lt;4&gt;[ 7290.415597]  [&lt;ffffffff81038d0c&gt;] ? __enqueue_entity+0x7c/0x80
&lt;4&gt;[ 7290.415616]  [&lt;ffffffff81039201&gt;] ? enqueue_task_fair+0x111/0x150
&lt;4&gt;[ 7290.415636]  [&lt;ffffffff8102e53e&gt;] bad_area_nosemaphore+0xe/0x10
&lt;4&gt;[ 7290.415656]  [&lt;ffffffff8102e8fa&gt;] do_page_fault+0x26a/0x320
&lt;4&gt;[ 7290.415674]  [&lt;ffffffff813905df&gt;] page_fault+0x1f/0x30
&lt;4&gt;[ 7290.415697]  [&lt;ffffffffa0dd53a1&gt;] ? iwl3945_rx_reply_tx+0xc1/0x450 [iwl3945]
&lt;4&gt;[ 7290.415723]  [&lt;ffffffffa0dc8c47&gt;] iwl3945_irq_tasklet+0x657/0x1740 [iwl3945]
&lt;4&gt;[ 7290.415746]  [&lt;ffffffff8138fc60&gt;] ? _spin_unlock+0x30/0x60
&lt;4&gt;[ 7290.415764]  [&lt;ffffffff81049a21&gt;] tasklet_action+0x101/0x110
&lt;4&gt;[ 7290.415783]  [&lt;ffffffff8104a3d0&gt;] __do_softirq+0xc0/0x160
&lt;4&gt;[ 7290.415801]  [&lt;ffffffff8100d01c&gt;] call_softirq+0x1c/0x30
&lt;4&gt;[ 7290.415818]  [&lt;ffffffff8100eff5&gt;] do_softirq+0x75/0xb0
&lt;4&gt;[ 7290.415835]  [&lt;ffffffff81049ee5&gt;] irq_exit+0x95/0xa0
&lt;4&gt;[ 7290.415852]  [&lt;ffffffff8100e547&gt;] do_IRQ+0x77/0xf0
&lt;4&gt;[ 7290.415869]  [&lt;ffffffff8100c7d3&gt;] ret_from_intr+0x0/0xf
&lt;4&gt;[ 7290.415883]  &lt;EOI&gt;  [&lt;ffffffff81234efa&gt;] ? acpi_idle_enter_bm+0x270/0x2a5
&lt;4&gt;[ 7290.415911]  [&lt;ffffffff81234f04&gt;] ? acpi_idle_enter_bm+0x27a/0x2a5
&lt;4&gt;[ 7290.415931]  [&lt;ffffffff81234efa&gt;] ? acpi_idle_enter_bm+0x270/0x2a5
&lt;4&gt;[ 7290.415952]  [&lt;ffffffff812c11f3&gt;] ? cpuidle_idle_call+0x93/0xf0
&lt;4&gt;[ 7290.415971]  [&lt;ffffffff8100b0d7&gt;] ? cpu_idle+0xa7/0x110
&lt;4&gt;[ 7290.415989]  [&lt;ffffffff8137b3d5&gt;] ? rest_init+0x75/0x80
&lt;4&gt;[ 7290.416007]  [&lt;ffffffff8158cd0a&gt;] ? start_kernel+0x3a7/0x3b3
&lt;4&gt;[ 7290.416026]  [&lt;ffffffff8158c315&gt;] ? x86_64_start_reservations+0x125/0x129
&lt;4&gt;[ 7290.416047]  [&lt;ffffffff8158c3fd&gt;] ? x86_64_start_kernel+0xe4/0xeb

Reported-by: Maxim Levitsky &lt;maximlevitsky@gmail.com&gt;
Tested-by: Maxim Levitsky &lt;maximlevitsky@gmail.com&gt;
Signed-off-by: Zhu Yi &lt;yi.zhu@intel.com&gt;
Signed-off-by: Reinette Chatre &lt;reinette.chatre@intel.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>xen: fix hang on suspend.</title>
<updated>2010-01-18T18:19:44Z</updated>
<author>
<name>Ian Campbell</name>
<email>ian.campbell@citrix.com</email>
</author>
<published>2009-12-17T13:57:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a111c28a5d47bc15ed6b644a0b7c69d748c1bdb2'/>
<id>urn:sha1:a111c28a5d47bc15ed6b644a0b7c69d748c1bdb2</id>
<content type='text'>
commit c5cae661d6cf808b6984762f763261adf35f3eb7 upstream.

In 65f63384 "xen: improve error handling in do_suspend" I said:
    - xs_suspend()/xs_resume() and dpm_suspend_noirq()/dpm_resume_noirq() were not
      nested in the obvious way.
and changed the ordering of the calls as so:
    BEFORE		AFTER
    xs_suspend		dpm_suspend_noirq
    dpm_suspend_noirq	xs_suspend
    *SUSPEND*		*SUSPEND*
    dpm_resume_noirq	dpm_resume_noirq
    xs_resume		xs_resume
Clearly this is not an improvement and I was talking rubbish.

In particular the new ordering is susceptible to a hang if a xenstore write is
in progress at the point at which the suspend kicks in. When the suspend
process calls xs_suspend it tries to take the request_mutex but if a write is
in progress it could be looping in xenbus_xs.c:read_reply() waiting for
something to arrive on &amp;xs_state.reply_list while holding the request_mutex
(taken in the caller of read_reply).

However if we have done dpm_suspend_noirq before xs_suspend then we won't get
any more xenstore interrupts and process_msg() will never be woken up to add
anything to the reply_list.

Fix this by calling xs_suspend before dpm_suspend_noirq. If dpm_suspend_noirq
fails then make sure we go through the xs_suspend_cancel() code path.

Signed-off-by: Ian Campbell &lt;ian.campbell@citrix.com&gt;
Acked-by: Jeremy Fitzhardinge &lt;jeremy.fitzhardinge@citrix.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>hwmon: (adt7462) Fix pin 28 monitoring</title>
<updated>2010-01-18T18:19:43Z</updated>
<author>
<name>Roger Blofeld</name>
<email>blofeldus@yahoo.com</email>
</author>
<published>2010-01-10T19:52:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a61dcb0c6ac2aac895a17b37dcbe57b249a3d826'/>
<id>urn:sha1:a61dcb0c6ac2aac895a17b37dcbe57b249a3d826</id>
<content type='text'>
commit bb595c923bc51dff9cdd112de18deb57ac7945d2 upstream.

The ADT7462_PIN28_VOLT value is a 4-bit field, so the corresponding
shift must be 4.

Signed-off-by: Roger Blofeld &lt;blofeldus@yahoo.com&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: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs</title>
<updated>2010-01-18T18:19:42Z</updated>
<author>
<name>Yong Wang</name>
<email>yong.y.wang@linux.intel.com</email>
</author>
<published>2010-01-10T19:52:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4052fbfb24712ee7bb31c4c813d551712d7a4e4e'/>
<id>urn:sha1:4052fbfb24712ee7bb31c4c813d551712d7a4e4e</id>
<content type='text'>
commit 1fe63ab47a617ee95f562eaa7ddbbc59981ff8c6 upstream.

The max junction temperature of Atom N450/D410/D510 CPUs is 100 degrees
Celsius. Since these CPUs are always coupled with Intel NM10 chipset in
one package, the best way to verify whether an Atom CPU is N450/D410/D510
is to check the host bridge device.

Signed-off-by: Yong Wang &lt;yong.y.wang@intel.com&gt;
Acked-by: Huaxu Wan &lt;huaxu.wan@intel.com&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>mmc_block: fix queue cleanup</title>
<updated>2010-01-18T18:19:36Z</updated>
<author>
<name>Adrian Hunter</name>
<email>adrian.hunter@nokia.com</email>
</author>
<published>2010-01-08T22:43:00Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e0abcea649db45223c7df49df5db04dc1aa3a271'/>
<id>urn:sha1:e0abcea649db45223c7df49df5db04dc1aa3a271</id>
<content type='text'>
commit 5fa83ce284a4b7cd9dcfadd01500b0ed4ab9b740 upstream.

The main bug was that 'blk_cleanup_queue()' was called while the block
device could still be in use, for example, because the card was removed
while files were still open.

In addition, to be sure that 'mmc_request()' will get called for all new
requests (so it can error them out), the queue is emptied during cleanup.
This is done after the worker thread is stopped to avoid racing with it.

Finally, it is not a device error for this to be happening, so quiet the
(sometimes very many) error messages.

Signed-off-by: Adrian Hunter &lt;adrian.hunter@nokia.com&gt;
Cc: &lt;linux-mmc@vger.kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

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