<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers, branch v3.12.1</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers?h=v3.12.1</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers?h=v3.12.1'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-11-20T20:37:37Z</updated>
<entry>
<title>usbcore: set lpm_capable field for LPM capable root hubs</title>
<updated>2013-11-20T20:37:37Z</updated>
<author>
<name>Xenia Ragiadakou</name>
<email>burzalodowa@gmail.com</email>
</author>
<published>2013-08-31T15:09:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=60e102ac73cd40069d077014c93c86dc7205cb68'/>
<id>urn:sha1:60e102ac73cd40069d077014c93c86dc7205cb68</id>
<content type='text'>
commit 9df89d85b407690afa46ddfbccc80bec6869971d upstream.

This patch sets the lpm_capable field for root hubs with LPM capabilities.

Signed-off-by: Xenia Ragiadakou &lt;burzalodowa@gmail.com&gt;
Reported-by: Martin MOKREJS &lt;mmokrejs@gmail.com&gt;
Suggested-by: Alan Stern &lt;stern@rowland.harvard.edu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>backlight: atmel-pwm-bl: fix deferred probe from __init</title>
<updated>2013-11-20T20:37:36Z</updated>
<author>
<name>Johan Hovold</name>
<email>jhovold@gmail.com</email>
</author>
<published>2013-09-23T14:27:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=beb9294315a7e3eb581bd3ef8536478e4e207871'/>
<id>urn:sha1:beb9294315a7e3eb581bd3ef8536478e4e207871</id>
<content type='text'>
commit 9d3fde86b15303decea632c929fbf1f3ae4501f2 upstream.

Move probe out of __init section and don't use platform_driver_probe
which cannot be used with deferred probing.

Since commit e9354576 ("gpiolib: Defer failed gpio requests by default")
this driver might return -EPROBE_DEFER if a gpio_request fails.

Cc: Richard Purdie &lt;rpurdie@rpsys.net&gt;
Cc: Jingoo Han &lt;jg1.han@samsung.com&gt;
Cc: Jean-Christophe Plagniol-Villard &lt;plagnioj@jcrosoft.com&gt;
Signed-off-by: Johan Hovold &lt;jhovold@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>misc: atmel_pwm: add deferred-probing support</title>
<updated>2013-11-20T20:37:36Z</updated>
<author>
<name>Johan Hovold</name>
<email>jhovold@gmail.com</email>
</author>
<published>2013-10-22T16:32:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0fe6a2bc2f2ee462d158c737bae7c50ab72b6b57'/>
<id>urn:sha1:0fe6a2bc2f2ee462d158c737bae7c50ab72b6b57</id>
<content type='text'>
commit 5c6d6fd1564138ad048564e48639f842714a90c6 upstream.

Two drivers (atmel-pwm-bl and leds-atmel-pwm) currently depend on the
atmel_pwm driver to have bound to any pwm-device before their devices
are probed.

Support deferred probing of such devices by making sure to return
-EPROBE_DEFER from pwm_channel_alloc when no pwm-device has yet been
bound.

Signed-off-by: Johan Hovold &lt;jhovold@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>USB: add new zte 3g-dongle's pid to option.c</title>
<updated>2013-11-20T20:37:36Z</updated>
<author>
<name>Rui li</name>
<email>li.rui27@zte.com.cn</email>
</author>
<published>2013-10-25T02:57:21Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=eef0a12514c401e3ace96fa4bfaac2bec0e05e19'/>
<id>urn:sha1:eef0a12514c401e3ace96fa4bfaac2bec0e05e19</id>
<content type='text'>
commit 0636fc507a976cdc40f21bdbcce6f0b98ff1dfe9 upstream.

Signed-off-by: Rui li &lt;li.rui27@zte.com.cn&gt;
Cc: stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>hyperv-fb: add pci stub</title>
<updated>2013-11-20T20:37:36Z</updated>
<author>
<name>Gerd Hoffmann</name>
<email>kraxel@redhat.com</email>
</author>
<published>2013-10-02T11:55:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=65c27e2766048495840d30e7ecf5ef90e5482136'/>
<id>urn:sha1:65c27e2766048495840d30e7ecf5ef90e5482136</id>
<content type='text'>
commit 7ad9684721606efbfb9b347346816e1e6baff8bb upstream.

This patch adds a pci stub driver to hyper-fb.  The hyperv framebuffer
driver will bind to the pci device then, so linux kernel and userspace
know there is a proper kernel driver for the device active.  lspci shows
this for example:

[root@dhcp231 ~]# lspci -vs8
00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual
VGA (prog-if 00 [VGA controller])
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at f8000000 (32-bit, non-prefetchable) [size=64M]
        Expansion ROM at &lt;unassigned&gt; [disabled]
        Kernel driver in use: hyperv_fb

Another effect is that the xorg vesa driver will not attach to the
device and thus the Xorg server will automatically use the fbdev
driver instead.

Signed-off-by: Gerd Hoffmann &lt;kraxel@redhat.com&gt;
Acked-by: Haiyang Zhang &lt;haiyangz@microsoft.com&gt;
Signed-off-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>cxgb3: Fix length calculation in write_ofld_wr() on 32-bit architectures</title>
<updated>2013-11-20T20:37:36Z</updated>
<author>
<name>Ben Hutchings</name>
<email>ben@decadent.org.uk</email>
</author>
<published>2013-10-27T21:02:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=28803de32124109eba3b6f5c2fc4b58481082108'/>
<id>urn:sha1:28803de32124109eba3b6f5c2fc4b58481082108</id>
<content type='text'>
[ Upstream commit 262e827fe745642589450ae241b7afd3912c3f25 ]

The length calculation here is now invalid on 32-bit architectures,
since sk_buff::tail is a pointer and sk_buff::transport_header is
an integer offset:

drivers/net/ethernet/chelsio/cxgb3/sge.c: In function 'write_ofld_wr':
drivers/net/ethernet/chelsio/cxgb3/sge.c:1603:9: warning: passing argument 4 of 'make_sgl' makes integer from pointer without a cast [enabled by default]
         adap-&gt;pdev);
         ^
drivers/net/ethernet/chelsio/cxgb3/sge.c:964:28: note: expected 'unsigned int' but argument is of type 'sk_buff_data_t'
 static inline unsigned int make_sgl(const struct sk_buff *skb,
                            ^

Use the appropriate skb accessor functions.

Compile-tested only.

Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
Fixes: 1a37e412a022 ('net: Use 16bits for *_headers fields of struct skbuff')
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>xen-netback: use jiffies_64 value to calculate credit timeout</title>
<updated>2013-11-20T20:37:36Z</updated>
<author>
<name>Wei Liu</name>
<email>wei.liu2@citrix.com</email>
</author>
<published>2013-10-28T12:07:57Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b6842aabed83d7e22f11a6b24f38be874a4b2320'/>
<id>urn:sha1:b6842aabed83d7e22f11a6b24f38be874a4b2320</id>
<content type='text'>
[ Upstream commit 059dfa6a93b779516321e5112db9d7621b1367ba ]

time_after_eq() only works if the delta is &lt; MAX_ULONG/2.

For a 32bit Dom0, if netfront sends packets at a very low rate, the time
between subsequent calls to tx_credit_exceeded() may exceed MAX_ULONG/2
and the test for timer_after_eq() will be incorrect. Credit will not be
replenished and the guest may become unable to send packets (e.g., if
prior to the long gap, all credit was exhausted).

Use jiffies_64 variant to mitigate this problem for 32bit Dom0.

Suggested-by: Jan Beulich &lt;jbeulich@suse.com&gt;
Signed-off-by: Wei Liu &lt;wei.liu2@citrix.com&gt;
Reviewed-by: David Vrabel &lt;david.vrabel@citrix.com&gt;
Cc: Ian Campbell &lt;ian.campbell@citrix.com&gt;
Cc: Jason Luan &lt;jianhai.luan@oracle.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>virtio-net: correctly handle cpu hotplug notifier during resuming</title>
<updated>2013-11-20T20:37:36Z</updated>
<author>
<name>Jason Wang</name>
<email>jasowang@redhat.com</email>
</author>
<published>2013-10-29T07:11:07Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5a2851884a79b740cf4af66149e1ba594357a92c'/>
<id>urn:sha1:5a2851884a79b740cf4af66149e1ba594357a92c</id>
<content type='text'>
[ Upstream commit ec9debbd9a88d8ea86c488d6ffcac419ee7d46d9 ]

commit 3ab098df35f8b98b6553edc2e40234af512ba877 (virtio-net: don't respond to
cpu hotplug notifier if we're not ready) tries to bypass the cpu hotplug
notifier by checking the config_enable and does nothing is it was false. So it
need to try to hold the config_lock mutex which may happen in atomic
environment which leads the following warnings:

[  622.944441] CPU0 attaching NULL sched-domain.
[  622.944446] CPU1 attaching NULL sched-domain.
[  622.944485] CPU0 attaching NULL sched-domain.
[  622.950795] BUG: sleeping function called from invalid context at kernel/mutex.c:616
[  622.950796] in_atomic(): 1, irqs_disabled(): 1, pid: 10, name: migration/1
[  622.950796] no locks held by migration/1/10.
[  622.950798] CPU: 1 PID: 10 Comm: migration/1 Not tainted 3.12.0-rc5-wl-01249-gb91e82d #317
[  622.950799] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[  622.950802]  0000000000000000 ffff88001d42dba0 ffffffff81a32f22 ffff88001bfb9c70
[  622.950803]  ffff88001d42dbb0 ffffffff810edb02 ffff88001d42dc38 ffffffff81a396ed
[  622.950805]  0000000000000046 ffff88001d42dbe8 ffffffff810e861d 0000000000000000
[  622.950805] Call Trace:
[  622.950810]  [&lt;ffffffff81a32f22&gt;] dump_stack+0x54/0x74
[  622.950815]  [&lt;ffffffff810edb02&gt;] __might_sleep+0x112/0x114
[  622.950817]  [&lt;ffffffff81a396ed&gt;] mutex_lock_nested+0x3c/0x3c6
[  622.950818]  [&lt;ffffffff810e861d&gt;] ? up+0x39/0x3e
[  622.950821]  [&lt;ffffffff8153ea7c&gt;] ? acpi_os_signal_semaphore+0x21/0x2d
[  622.950824]  [&lt;ffffffff81565ed1&gt;] ? acpi_ut_release_mutex+0x5e/0x62
[  622.950828]  [&lt;ffffffff816d04ec&gt;] virtnet_cpu_callback+0x33/0x87
[  622.950830]  [&lt;ffffffff81a42576&gt;] notifier_call_chain+0x3c/0x5e
[  622.950832]  [&lt;ffffffff810e86a8&gt;] __raw_notifier_call_chain+0xe/0x10
[  622.950835]  [&lt;ffffffff810c5556&gt;] __cpu_notify+0x20/0x37
[  622.950836]  [&lt;ffffffff810c5580&gt;] cpu_notify+0x13/0x15
[  622.950838]  [&lt;ffffffff81a237cd&gt;] take_cpu_down+0x27/0x3a
[  622.950841]  [&lt;ffffffff81136289&gt;] stop_machine_cpu_stop+0x93/0xf1
[  622.950842]  [&lt;ffffffff81136167&gt;] cpu_stopper_thread+0xa0/0x12f
[  622.950844]  [&lt;ffffffff811361f6&gt;] ? cpu_stopper_thread+0x12f/0x12f
[  622.950847]  [&lt;ffffffff81119710&gt;] ? lock_release_holdtime.part.7+0xa3/0xa8
[  622.950848]  [&lt;ffffffff81135e4b&gt;] ? cpu_stop_should_run+0x3f/0x47
[  622.950850]  [&lt;ffffffff810ea9b0&gt;] smpboot_thread_fn+0x1c5/0x1e3
[  622.950852]  [&lt;ffffffff810ea7eb&gt;] ? lg_global_unlock+0x67/0x67
[  622.950854]  [&lt;ffffffff810e36b7&gt;] kthread+0xd8/0xe0
[  622.950857]  [&lt;ffffffff81a3bfad&gt;] ? wait_for_common+0x12f/0x164
[  622.950859]  [&lt;ffffffff810e35df&gt;] ? kthread_create_on_node+0x124/0x124
[  622.950861]  [&lt;ffffffff81a45ffc&gt;] ret_from_fork+0x7c/0xb0
[  622.950862]  [&lt;ffffffff810e35df&gt;] ? kthread_create_on_node+0x124/0x124
[  622.950876] smpboot: CPU 1 is now offline
[  623.194556] SMP alternatives: lockdep: fixing up alternatives
[  623.194559] smpboot: Booting Node 0 Processor 1 APIC 0x1
...

A correct fix is to unregister the hotcpu notifier during restore and register a
new one in resume.

Reported-by: Fengguang Wu &lt;fengguang.wu@intel.com&gt;
Tested-by: Fengguang Wu &lt;fengguang.wu@intel.com&gt;
Cc: Wanlong Gao &lt;gaowanlong@cn.fujitsu.com&gt;
Cc: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
Cc: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Signed-off-by: Jason Wang &lt;jasowang@redhat.com&gt;
Acked-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Reviewed-by: Wanlong Gao &lt;gaowanlong@cn.fujitsu.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>net/mlx4_core: Fix call to __mlx4_unregister_mac</title>
<updated>2013-11-20T20:37:35Z</updated>
<author>
<name>Jack Morgenstein</name>
<email>jackm@dev.mellanox.co.il</email>
</author>
<published>2013-11-03T08:04:07Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=65879edf74e6e36157e3d4d3254eae1dd77287a7'/>
<id>urn:sha1:65879edf74e6e36157e3d4d3254eae1dd77287a7</id>
<content type='text'>
[ Upstream commit c32b7dfbb1dfb3f0a68f250deff65103c8bb704a ]

In function mlx4_master_deactivate_admin_state() __mlx4_unregister_mac was
called using the MAC index. It should be called with the value of the MAC itself.

Signed-off-by: Jack Morgenstein &lt;jackm@dev.mellanox.co.il&gt;
Signed-off-by: Or Gerlitz &lt;ogerlitz@mellanox.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'usb-3.12-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb</title>
<updated>2013-11-01T19:23:56Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2013-11-01T19:23:56Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9119e33e507d3b8fe234f2c2bafd3199ea2e883b'/>
<id>urn:sha1:9119e33e507d3b8fe234f2c2bafd3199ea2e883b</id>
<content type='text'>
Pull USB fixes from Greg KH:
 "Here is a set of patches that revert all of the changes done to the
  pl2303 USB serial driver in the 3.12-rc timeframe, as it turns out
  they break some devices that work just fine on 3.11.  As it's not a
  good idea to break working systems, drop them all and they will be
  reworked for future kernel versions such that there is no breakage.

  I've also included a MAINTAINERS update for the USB serial subsystem
  and a new device id for the ftdi_sio driver as well"

* tag 'usb-3.12-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb:
  USB: serial: ftdi_sio: add id for Z3X Box device
  USB: Maintainers change for usb serial drivers
  Revert "USB: pl2303: restrict the divisor based baud rate encoding method to the "HX" chip type"
  Revert "usb: pl2303: fix+improve the divsor based baud rate encoding method"
  Revert "usb: pl2303: do not round to the next nearest standard baud rate for the divisor based baud rate encoding method"
  Revert "usb: pl2303: remove 500000 baud from the list of standard baud rates"
  Revert "usb: pl2303: move the two baud rate encoding methods to separate functions"
  Revert "usb: pl2303: increase the allowed baud rate range for the divisor based encoding method"
  Revert "usb: pl2303: also use the divisor based baud rate encoding method for baud rates &lt; 115200 with HX chips"
  Revert "usb: pl2303: add two comments concerning the supported baud rates with HX chips"
  Revert "pl2303: simplify the else-if contruct for type_1 chips in pl2303_startup()"
  Revert "pl2303: improve the chip type information output on startup"
  Revert "pl2303: improve the chip type detection/distinction"
  Revert "USB: pl2303: distinguish between original and cloned HX chips"
</content>
</entry>
</feed>
