<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/net/can/usb, branch linux-3.4.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.4.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.4.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2015-04-14T09:33:45Z</updated>
<entry>
<title>can: peak_usb: fix cleanup sequence order in case of error during init</title>
<updated>2015-04-14T09:33:45Z</updated>
<author>
<name>Stephane Grosjean</name>
</author>
<published>2014-11-28T12:49:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3a95358ade4950574185c5b58835693836aa4ecb'/>
<id>urn:sha1:3a95358ade4950574185c5b58835693836aa4ecb</id>
<content type='text'>
commit af35d0f1cce7a990286e2b94c260a2c2d2a0e4b0 upstream.

This patch sets the correct reverse sequence order to the instructions
set to run, when any failure occurs during the initialization steps.
It also adds the missing unregistration call of the can device if the
failure appears after having been registered.

Signed-off-by: Stephane Grosjean &lt;s.grosjean@peak-system.com&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Zefan Li &lt;lizefan@huawei.com&gt;
</content>
</entry>
<entry>
<title>can: peak_usb: fix memset() usage</title>
<updated>2015-04-14T09:33:45Z</updated>
<author>
<name>Stephane Grosjean</name>
</author>
<published>2014-11-28T13:08:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b476ea71ec15a885cab76dc1aa22abd6f24b9213'/>
<id>urn:sha1:b476ea71ec15a885cab76dc1aa22abd6f24b9213</id>
<content type='text'>
commit dc50ddcd4c58a5a0226038307d6ef884bec9f8c2 upstream.

This patchs fixes a misplaced call to memset() that fills the request
buffer with 0. The problem was with sending PCAN_USBPRO_REQ_FCT
requests, the content set by the caller was thus lost.

With this patch, the memory area is zeroed only when requesting info
from the device.

Signed-off-by: Stephane Grosjean &lt;s.grosjean@peak-system.com&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Zefan Li &lt;lizefan@huawei.com&gt;
</content>
</entry>
<entry>
<title>can: esd_usb2: fix memory leak on disconnect</title>
<updated>2015-02-02T09:05:22Z</updated>
<author>
<name>Alexey Khoroshilov</name>
</author>
<published>2014-10-10T20:31:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=11c9fc9d691d0a6669319c30f4da60c1d425801e'/>
<id>urn:sha1:11c9fc9d691d0a6669319c30f4da60c1d425801e</id>
<content type='text'>
commit efbd50d2f62fc1f69a3dcd153e63ba28cc8eb27f upstream.

It seems struct esd_usb2 dev is not deallocated on disconnect. The patch adds
the missing deallocation.

Found by Linux Driver Verification project (linuxtesting.org).

Signed-off-by: Alexey Khoroshilov &lt;khoroshilov@ispras.ru&gt;
Acked-by: Matthias Fuchs &lt;matthias.fuchs@esd.eu&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Zefan Li &lt;lizefan@huawei.com&gt;
</content>
</entry>
<entry>
<title>can: pcan_usb: fix wrong memcpy() bytes length</title>
<updated>2013-08-20T15:26:28Z</updated>
<author>
<name>Stephane Grosjean</name>
</author>
<published>2013-08-09T09:44:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2efb739b6c863a77cfc362b69f755c32805a5fc2'/>
<id>urn:sha1:2efb739b6c863a77cfc362b69f755c32805a5fc2</id>
<content type='text'>
commit 3c322a56b01695df15c70bfdc2d02e0ccd80654e upstream.

Fix possibly wrong memcpy() bytes length since some CAN records received from
PCAN-USB could define a DLC field in range [9..15].
In that case, the real DLC value MUST be used to move forward the record pointer
but, only 8 bytes max. MUST be copied into the data field of the struct
can_frame object of the skb given to the network core.

Signed-off-by: Stephane Grosjean &lt;s.grosjean@peak-system.com&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&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>can: peak_usb: fix hwtstamp assignment</title>
<updated>2012-12-03T19:47:09Z</updated>
<author>
<name>Oliver Hartkopp</name>
</author>
<published>2012-11-21T21:43:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5e937c8ffe7d6ba56a699684a4bc5f6b3edd05a5'/>
<id>urn:sha1:5e937c8ffe7d6ba56a699684a4bc5f6b3edd05a5</id>
<content type='text'>
commit c9faaa09e2a1335678f09c70a0d0eda095564bab upstream.

The skb-&gt;tstamp is set to the hardware timestamp when available in the USB
urb message. This leads to user visible timestamps which contain the 'uptime'
of the USB adapter - and not the usual system generated timestamp.

Fix this wrong assignment by applying the available hardware timestamp to the
skb_shared_hwtstamps data structure - which is intended for this purpose.

Signed-off-by: Oliver Hartkopp &lt;socketcan@hartkopp.net&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>can: usb: PCAN-USB Pro: fix mem leaks in pcan_usb_pro_init() on error paths</title>
<updated>2012-04-16T19:34:50Z</updated>
<author>
<name>Jesper Juhl</name>
</author>
<published>2012-04-11T21:23:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a49bcabedc18319f673319d5e71b5751e3978179'/>
<id>urn:sha1:a49bcabedc18319f673319d5e71b5751e3978179</id>
<content type='text'>
If either call to pcan_usb_pro_send_req() in
drivers/net/can/usb/peak_usb/pcan_usb_pro.c::pcan_usb_pro_init()
fails, we'll leak the memory we allocated to 'usb_if' with kzalloc()
when the 'usb_if' variable goes out of scope without having been
assigned to anything as we 'return err;'.
Fix this by adding appropriate kfree(usb_if) calls to the error paths.

Signed-off-by: Jesper Juhl &lt;jj@chaosbits.net&gt;
Acked-by: Stephane Grosjean &lt;s.grosjean@peak-system.com&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
</content>
</entry>
<entry>
<title>can: peak_usb: PCAN-USB specific part: fix little endian usage</title>
<updated>2012-03-07T14:51:01Z</updated>
<author>
<name>Stephane Grosjean</name>
</author>
<published>2012-03-07T14:31:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1ccba2103a8b3a1041f261301b08b9e16f76df8a'/>
<id>urn:sha1:1ccba2103a8b3a1041f261301b08b9e16f76df8a</id>
<content type='text'>
That patch fixes some bad usage of two little-endian variables, which lead to
some warning/error when building the peak_usb driver.

Reported-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Acked-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Stephane Grosjean &lt;s.grosjean@peak-system.com&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
</content>
</entry>
<entry>
<title>can: usb: PEAK-System Technik PCAN-USB Pro specific part</title>
<updated>2012-03-03T16:40:58Z</updated>
<author>
<name>Stephane Grosjean</name>
</author>
<published>2012-03-02T15:13:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d8a199355f8f8a0797c00d98788d7282c9ea38bd'/>
<id>urn:sha1:d8a199355f8f8a0797c00d98788d7282c9ea38bd</id>
<content type='text'>
This patch adds the specific part which handles the PCAN-USB Pro adapter
from PEAK-System Technik (http://www.peak-system.com). The PCAN-USB Pro
adapter is a dual-channel USB 2.0 adapter compliant with CAN specifications

Tested-by: Oliver Hartkopp &lt;socketcan@hartkopp.net&gt;
Acked-by: Wolfgang Grandegger &lt;wg@grandegger.com&gt;
Signed-off-by: Stephane Grosjean &lt;s.grosjean@peak-system.com&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
</content>
</entry>
<entry>
<title>can: usb: PEAK-System Technik PCAN-USB specific part</title>
<updated>2012-03-03T16:40:55Z</updated>
<author>
<name>Stephane Grosjean</name>
</author>
<published>2012-03-02T15:13:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=46be265d3388339d8168c863791f0c7bbf3f2fed'/>
<id>urn:sha1:46be265d3388339d8168c863791f0c7bbf3f2fed</id>
<content type='text'>
This patch adds the specific part which handles the PCAN-USB adapter from
PEAK-System Technik (http://www.peak-system.com). The PCAN-USB adapter is
a sja1000 based, mono-channel USB 1.1 adapter compliant with CAN
specifications 2.0A (11-bit ID) and 2.0B (29-bit ID).

Tested-by: Oliver Hartkopp &lt;socketcan@hartkopp.net&gt;
Acked-by: Wolfgang Grandegger &lt;wg@grandegger.com&gt;
Signed-off-by: Stephane Grosjean &lt;s.grosjean@peak-system.com&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
</content>
</entry>
<entry>
<title>can: usb: PEAK-System Technik USB adapters driver core</title>
<updated>2012-03-03T16:40:51Z</updated>
<author>
<name>Stephane Grosjean</name>
</author>
<published>2012-03-02T15:13:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d'/>
<id>urn:sha1:bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d</id>
<content type='text'>
This patch adds the core of the peak_usb driver which handles PEAK-System
Technik PCAN USB adapters. It defines the parts which are common to the
PCAN-USB adapters: can network interfaces management, network-to/from-usb
data path interface, timestamps management...

Tested-by: Oliver Hartkopp &lt;socketcan@hartkopp.net&gt;
Acked-by: Wolfgang Grandegger &lt;wg@grandegger.com&gt;
Signed-off-by: Stephane Grosjean &lt;s.grosjean@peak-system.com&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
</content>
</entry>
</feed>
