<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/staging, branch v3.4.11</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/staging?h=v3.4.11</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/staging?h=v3.4.11'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-09-14T17:00:06Z</updated>
<entry>
<title>USB: winbond: remove __devinit* from the struct usb_device_id table</title>
<updated>2012-09-14T17:00:06Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2012-08-18T00:48:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5be8fc241c52f469cd8f2c9e4ebd66ce4ab9df34'/>
<id>urn:sha1:5be8fc241c52f469cd8f2c9e4ebd66ce4ab9df34</id>
<content type='text'>
commit 43a34695d9cd79c6659f09da6d3b0624f3dd169f upstream.

This structure needs to always stick around, even if CONFIG_HOTPLUG
is disabled, otherwise we can oops when trying to probe a device that
was added after the structure is thrown away.

Thanks to Fengguang Wu and Bjørn Mork for tracking this issue down.

Reported-by: Fengguang Wu &lt;fengguang.wu@intel.com&gt;
Reported-by: Bjørn Mork &lt;bjorn@mork.no&gt;
CC: Pavel Machek &lt;pavel@ucw.cz&gt;
CC: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
CC: "John W. Linville" &lt;linville@tuxdriver.com&gt;
CC: Eliad Peller &lt;eliad@wizery.com&gt;
CC: Devendra Naga &lt;devendra.aaru@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>USB: vt6656: remove __devinit* from the struct usb_device_id table</title>
<updated>2012-09-14T17:00:03Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2012-08-18T00:48:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=61fe808721d1b13c811f6d9a2809628e4ef6bf06'/>
<id>urn:sha1:61fe808721d1b13c811f6d9a2809628e4ef6bf06</id>
<content type='text'>
commit 4d088876f24887cd15a29db923f5f37db6a99f21 upstream.

This structure needs to always stick around, even if CONFIG_HOTPLUG
is disabled, otherwise we can oops when trying to probe a device that
was added after the structure is thrown away.

Thanks to Fengguang Wu and Bjørn Mork for tracking this issue down.

Reported-by: Fengguang Wu &lt;fengguang.wu@intel.com&gt;
Reported-by: Bjørn Mork &lt;bjorn@mork.no&gt;
CC: Forest Bond &lt;forest@alittletooquiet.net&gt;
CC: Marcos Paulo de Souza &lt;marcos.souza.org@gmail.com&gt;
CC: "David S. Miller" &lt;davem@davemloft.net&gt;
CC: Jesper Juhl &lt;jj@chaosbits.net&gt;
CC: Jiri Pirko &lt;jpirko@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>staging: zsmalloc: Finish conversion to a separate module</title>
<updated>2012-08-09T15:31:37Z</updated>
<author>
<name>Ben Hutchings</name>
<email>ben@decadent.org.uk</email>
</author>
<published>2012-06-20T01:31:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c7815406caf7efdd805e893caef4a63e61b7645e'/>
<id>urn:sha1:c7815406caf7efdd805e893caef4a63e61b7645e</id>
<content type='text'>
commit 069f101fa463351f528773d73b74e9b606b3f66a upstream.

ZSMALLOC is tristate, but the code has no MODULE_LICENSE and since it
depends on GPL-only symbols it cannot be loaded as a module.  This in
turn breaks zram which now depends on it.  I assume it's meant to be
Dual BSD/GPL like the other z-stuff.

There is also no module_exit, which will make it impossible to unload.
Add the appropriate module_init and module_exit declarations suggested
by comments.

Reported-by: Christian Ohm &lt;chr.ohm@gmx.net&gt;
References: http://bugs.debian.org/677273
Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
Reviewed-by: Jonathan Nieder &lt;jrnieder@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>staging:iio:ad7606: Re-add missing scale attribute</title>
<updated>2012-07-16T16:04:43Z</updated>
<author>
<name>Lars-Peter Clausen</name>
<email>lars@metafoo.de</email>
</author>
<published>2012-06-05T16:16:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a2db97f10ba81ce924323e580a223ce8d17d685c'/>
<id>urn:sha1:a2db97f10ba81ce924323e580a223ce8d17d685c</id>
<content type='text'>
commit 279bf2e57c30c9a4482b2b6ede11b31c41e35e78 upstream.

Commit 50ac23be ("staging:iio:adc:ad7606 add local define for chan_spec
structures.") accidentally removed the scale info_mask flag. This patch
adds it back again.

Signed-off-by: Lars-Peter Clausen &lt;lars@metafoo.de&gt;
Acked-by: Jonathan Cameron &lt;jic23@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
[herton: Backported to 3.4: info_mask was not used yet with another flag]
Signed-off-by: Herton R. Krzesinski &lt;herton@canonical.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>staging: r8712u: Add new USB IDs</title>
<updated>2012-07-16T16:03:50Z</updated>
<author>
<name>Lubomir Schmidt</name>
<email>gentoo.lubomir@googlemail.com</email>
</author>
<published>2012-06-15T20:12:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a4ab3b05fe0320bad00a1ba320d6fd4b9cd29643'/>
<id>urn:sha1:a4ab3b05fe0320bad00a1ba320d6fd4b9cd29643</id>
<content type='text'>
commit 3026b0e942c65c65c8fc80d391d004228b52b916 upstream.

There are two new devices for this driver.

Signed-off-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>persistent_ram: Fix buffer size clamping during writes</title>
<updated>2012-06-01T07:18:18Z</updated>
<author>
<name>Anton Vorontsov</name>
<email>anton.vorontsov@linaro.org</email>
</author>
<published>2012-05-12T00:17:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=bbe784b683f6e49bc345577fc5398344bc7c289e'/>
<id>urn:sha1:bbe784b683f6e49bc345577fc5398344bc7c289e</id>
<content type='text'>
commit 484dd30e016eb425b0de871357fff2c9bb93be45 upstream.

This is a longstanding bug, almost unnoticeable when calling
persistent_ram_write() for small buffers.

But when called for large data buffers, the write routine behaves
incorrectly, as the size may never update: instead of clamping
the size to the maximum buffer size, buffer_size_add_clamp() returns
an error (which is never checked by the write routine, btw).

To fix this, we now use buffer_size_add() that actually clamps the
size to the max value.

Also remove buffer_size_add_clamp(), it is no longer needed.

Signed-off-by: Anton Vorontsov &lt;anton.vorontsov@linaro.org&gt;
Acked-by: Colin Cross &lt;ccross@android.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drivers/staging/comedi/comedi_fops.c: add missing vfree</title>
<updated>2012-06-01T07:18:17Z</updated>
<author>
<name>Julia Lawall</name>
<email>Julia.Lawall@lip6.fr</email>
</author>
<published>2012-04-22T11:37:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d026b7150e38a1764d83fc57b6e4448d5e278eaf'/>
<id>urn:sha1:d026b7150e38a1764d83fc57b6e4448d5e278eaf</id>
<content type='text'>
commit abae41e6438b798e046d721b6ccdd55b4a398170 upstream.

aux_free is freed on all other exits from the function.  By removing the
return, we can benefit from the vfree already at the end of the function.

Signed-off-by: Julia Lawall &lt;Julia.Lawall@lip6.fr&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>staging: ozwpan: Fix bug where kfree is called twice.</title>
<updated>2012-04-26T19:40:53Z</updated>
<author>
<name>Rupesh Gujare</name>
<email>rgujare@ozmodevices.com</email>
</author>
<published>2012-04-25T22:54:58Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=89f21cc050d5eed8eeffee5b46297fb7a74ef9dd'/>
<id>urn:sha1:89f21cc050d5eed8eeffee5b46297fb7a74ef9dd</id>
<content type='text'>
Signed-off-by: Rupesh Gujare &lt;rgujare@ozmodevices.com&gt;
Signed-off-by: Chris Kelly &lt;ckelly@ozmodevices.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: octeon-ethernet: fix build errors by including interrupt.h</title>
<updated>2012-04-24T18:57:37Z</updated>
<author>
<name>Imre Kaloz</name>
<email>kaloz@openwrt.org</email>
</author>
<published>2012-04-19T10:27:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dc890df0a77cafe5f4a3d81c0dade637c27f1934'/>
<id>urn:sha1:dc890df0a77cafe5f4a3d81c0dade637c27f1934</id>
<content type='text'>
This patch fixes the following build failures:

drivers/staging/octeon/ethernet.c: In function 'cvm_oct_cleanup_module':
drivers/staging/octeon/ethernet.c:799:2: error: implicit declaration of function 'free_irq'
drivers/staging/octeon/ethernet-rx.c: In function 'cvm_oct_no_more_work':
drivers/staging/octeon/ethernet-rx.c:119:3: error: implicit declaration of function 'enable_irq'
drivers/staging/octeon/ethernet-rx.c: In function 'cvm_oct_do_interrupt':
drivers/staging/octeon/ethernet-rx.c:136:2: error: implicit declaration of function 'disable_irq_nosync'
drivers/staging/octeon/ethernet-rx.c: In function 'cvm_oct_rx_initialize':
drivers/staging/octeon/ethernet-rx.c:532:2: error: implicit declaration of function 'request_irq'
drivers/staging/octeon/ethernet-tx.c: In function 'cvm_oct_tx_initialize':
drivers/staging/octeon/ethernet-tx.c:712:2: error: implicit declaration of function 'request_irq'
drivers/staging/octeon/ethernet-tx.c: In function 'cvm_oct_tx_shutdown':
drivers/staging/octeon/ethernet-tx.c:723:2: error: implicit declaration of function 'free_irq'

Signed-off-by: Imre Kaloz &lt;kaloz@openwrt.org&gt;
Acked-by: David Daney &lt;david.daney@cavium.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: zcache: fix Kconfig crypto dependency</title>
<updated>2012-04-24T18:57:36Z</updated>
<author>
<name>Seth Jennings</name>
<email>sjenning@linux.vnet.ibm.com</email>
</author>
<published>2012-04-24T01:33:50Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=349ae79c0a3db1632ac4db955c53db05fc017bde'/>
<id>urn:sha1:349ae79c0a3db1632ac4db955c53db05fc017bde</id>
<content type='text'>
ZCACHE is a boolean in the Kconfig.  When selected, it
should require that CRYPTO be builtin (=y).

Currently, ZCACHE=y and CRYPTO=m is a valid configuration
when it should not be.

This patch changes the zcache Kconfig to enforce this
dependency.

Signed-off-by: Seth Jennings &lt;sjenning@linux.vnet.ibm.com&gt;
Acked-by: Konrad Rzeszutek Wilk &lt;konrad.wilk@oracle.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
