<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/git/stable/linux-stable.git/drivers/net/can, branch linux-3.6.y</title>
<subtitle>Linux kernel stable tree</subtitle>
<id>https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/atom?h=linux-3.6.y</id>
<link rel='self' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/atom?h=linux-3.6.y'/>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/'/>
<updated>2012-12-03T19:38:00+00:00</updated>
<entry>
<title>can: peak_usb: fix hwtstamp assignment</title>
<updated>2012-12-03T19:38:00+00:00</updated>
<author>
<name>Oliver Hartkopp</name>
<email>socketcan@hartkopp.net</email>
</author>
<published>2012-11-21T21:43:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=4735a28cf102492dde4c036f74b0c2d8318ed004'/>
<id>urn:sha1:4735a28cf102492dde4c036f74b0c2d8318ed004</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: mscan-mpc5xxx: fix return value check in mpc512x_can_get_clock()</title>
<updated>2012-10-07T15:39:35+00:00</updated>
<author>
<name>Wei Yongjun</name>
<email>yongjun_wei@trendmicro.com.cn</email>
</author>
<published>2012-09-21T07:09:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=b2be9b06f9f9682943fe274c0d3c07945e623e76'/>
<id>urn:sha1:b2be9b06f9f9682943fe274c0d3c07945e623e76</id>
<content type='text'>
commit f61bd0585dfc7d99db4936d7467de4ca8e2f7ea0 upstream.

In case of error, the function clk_get() returns ERR_PTR()
and never returns NULL pointer. The NULL test in the error
handling should be replaced with IS_ERR().

dpatch engine is used to auto generated this patch.
(https://github.com/weiyj/dpatch)

Signed-off-by: Wei Yongjun &lt;yongjun_wei@trendmicro.com.cn&gt;
Acked-by: Wolfgang Grandegger &lt;wg@grandegger.com&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: ti_hecc: fix oops during rmmod</title>
<updated>2012-09-21T10:54:53+00:00</updated>
<author>
<name>Marc Kleine-Budde</name>
<email>mkl@pengutronix.de</email>
</author>
<published>2012-09-19T12:58:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=ab04c8bd423edb03e2148350a091836c196107fc'/>
<id>urn:sha1:ab04c8bd423edb03e2148350a091836c196107fc</id>
<content type='text'>
This patch fixes an oops which occurs when unloading the driver, while the
network interface is still up. The problem is that first the io mapping is
teared own, then the CAN device is unregistered, resulting in accessing the
hardware's iomem:

[  172.744232] Unable to handle kernel paging request at virtual address c88b0040
[  172.752441] pgd = c7be4000
[  172.755645] [c88b0040] *pgd=87821811, *pte=00000000, *ppte=00000000
[  172.762207] Internal error: Oops: 807 [#1] PREEMPT ARM
[  172.767517] Modules linked in: ti_hecc(-) can_dev
[  172.772430] CPU: 0    Not tainted  (3.5.0alpha-00037-g3554cc0 #126)
[  172.778961] PC is at ti_hecc_close+0xb0/0x100 [ti_hecc]
[  172.784423] LR is at __dev_close_many+0x90/0xc0
[  172.789123] pc : [&lt;bf00c768&gt;]    lr : [&lt;c033be58&gt;]    psr: 60000013
[  172.789123] sp : c5c1de68  ip : 00040081  fp : 00000000
[  172.801025] r10: 00000001  r9 : c5c1c000  r8 : 00100100
[  172.806457] r7 : c5d0a48c  r6 : c5d0a400  r5 : 00000000  r4 : c5d0a000
[  172.813232] r3 : c88b0000  r2 : 00000001  r1 : c5d0a000  r0 : c5d0a000
[  172.820037] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
[  172.827423] Control: 10c5387d  Table: 87be4019  DAC: 00000015
[  172.833404] Process rmmod (pid: 600, stack limit = 0xc5c1c2f0)
[  172.839447] Stack: (0xc5c1de68 to 0xc5c1e000)
[  172.843994] de60:                   bf00c6b8 c5c1dec8 c5d0a000 c5d0a000 00200200 c033be58
[  172.852478] de80: c5c1de44 c5c1dec8 c5c1dec8 c033bf2c c5c1de90 c5c1de90 c5d0a084 c5c1de44
[  172.860992] dea0: c5c1dec8 c033c098 c061d3dc c5d0a000 00000000 c05edf28 c05edb34 c000d724
[  172.869476] dec0: 00000000 c033c2f8 c5d0a084 c5d0a084 00000000 c033c370 00000000 c5d0a000
[  172.877990] dee0: c05edb00 c033c3b8 c5d0a000 bf00d3ac c05edb00 bf00d7c8 bf00d7c8 c02842dc
[  172.886474] df00: c02842c8 c0282f90 c5c1c000 c05edb00 bf00d7c8 c0283668 bf00d7c8 00000000
[  172.894989] df20: c0611f98 befe2f80 c000d724 c0282d10 bf00d804 00000000 00000013 c0068a8c
[  172.903472] df40: c5c538e8 685f6974 00636365 c61571a8 c5cb9980 c61571a8 c6158a20 c00c9bc4
[  172.911987] df60: 00000000 00000000 c5cb9980 00000000 c5cb9980 00000000 c7823680 00000006
[  172.920471] df80: bf00d804 00000880 c5c1df8c 00000000 000d4267 befe2f80 00000001 b6d90068
[  172.928985] dfa0: 00000081 c000d5a0 befe2f80 00000001 befe2f80 00000880 b6d90008 00000008
[  172.937469] dfc0: befe2f80 00000001 b6d90068 00000081 00000001 00000000 befe2eac 00000000
[  172.945983] dfe0: 00000000 befe2b18 00023ba4 b6e6addc 60000010 befe2f80 a8e00190 86d2d344
[  172.954498] [&lt;bf00c768&gt;] (ti_hecc_close+0xb0/0x100 [ti_hecc]) from [&lt;c033be58&gt;] (__dev__registered_many+0xc0/0x2a0)
[  172.984161] [&lt;c033c098&gt;] (rollback_registered_many+0xc0/0x2a0) from [&lt;c033c2f8&gt;] (rollback_registered+0x20/0x30)
[  172.994750] [&lt;c033c2f8&gt;] (rollback_registered+0x20/0x30) from [&lt;c033c370&gt;] (unregister_netdevice_queue+0x68/0x98)
[  173.005401] [&lt;c033c370&gt;] (unregister_netdevice_queue+0x68/0x98) from [&lt;c033c3b8&gt;] (unregister_netdev+0x18/0x20)
[  173.015899] [&lt;c033c3b8&gt;] (unregister_netdev+0x18/0x20) from [&lt;bf00d3ac&gt;] (ti_hecc_remove+0x60/0x80 [ti_hecc])
[  173.026245] [&lt;bf00d3ac&gt;] (ti_hecc_remove+0x60/0x80 [ti_hecc]) from [&lt;c02842dc&gt;] (platform_drv_remove+0x14/0x18)
[  173.036712] [&lt;c02842dc&gt;] (platform_drv_remove+0x14/0x18) from [&lt;c0282f90&gt;] (__device_release_driver+0x7c/0xbc)

Cc: stable &lt;stable@vger.kernel.org&gt;
Cc: Anant Gole &lt;anantgole@ti.com&gt;
Tested-by: Jan Luebbe &lt;jlu@pengutronix.de&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
</content>
</entry>
<entry>
<title>can: janz-ican3: fix support for older hardware revisions</title>
<updated>2012-09-21T10:54:52+00:00</updated>
<author>
<name>Ira W. Snyder</name>
<email>iws@ovro.caltech.edu</email>
</author>
<published>2012-09-11T22:58:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=e21093ef6fb4cbecdf926102286dbe280ae965db'/>
<id>urn:sha1:e21093ef6fb4cbecdf926102286dbe280ae965db</id>
<content type='text'>
The Revision 1.0 Janz CMOD-IO Carrier Board does not have support for
the reset registers. To support older hardware, the code is changed to
use the hardware reset register on the Janz VMOD-ICAN3 hardware itself.

Cc: stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Ira W. Snyder &lt;iws@ovro.caltech.edu&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
</content>
</entry>
<entry>
<title>can: mcp251x: avoid repeated frame bug</title>
<updated>2012-09-03T18:12:06+00:00</updated>
<author>
<name>Benoît Locher</name>
<email>Benoit.Locher@skf.com</email>
</author>
<published>2012-08-27T13:02:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=cab32f39dcc5b35db96497dc0a026b5dea76e4e7'/>
<id>urn:sha1:cab32f39dcc5b35db96497dc0a026b5dea76e4e7</id>
<content type='text'>
The MCP2515 has a silicon bug causing repeated frame transmission, see section
5 of MCP2515 Rev. B Silicon Errata Revision G (March 2007).

Basically, setting TXBnCTRL.TXREQ in either SPI mode (00 or 11) will eventually
cause the bug. The workaround proposed by Microchip is to use mode 00 and send
a RTS command on the SPI bus to initiate the transmission.

Cc: &lt;stable@vger.kernel.org&gt;
Signed-off-by: Benoît Locher &lt;Benoit.Locher@skf.com&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
</content>
</entry>
<entry>
<title>can: sja1000_platform: fix wrong flag IRQF_SHARED for interrupt sharing</title>
<updated>2012-08-24T08:54:05+00:00</updated>
<author>
<name>Sven Schmitt</name>
<email>sven.schmitt@volkswagen.de</email>
</author>
<published>2012-08-09T12:46:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=da3d50ef308d53f216f1f92f4971f245c13e9f65'/>
<id>urn:sha1:da3d50ef308d53f216f1f92f4971f245c13e9f65</id>
<content type='text'>
The sja1000 platform driver wrongly assumes that a shared IRQ is indicated
with the IRQF_SHARED flag in irq resource flags. This patch changes the
driver to handle the correct flag IORESOURCE_IRQ_SHAREABLE instead.

There are no mainline users of the platform driver which wrongly make use
of IRQF_SHARED.

Signed-off-by: Sven Schmitt &lt;sven.schmitt@volkswagen.de&gt;
Acked-by: Yegor Yefremov &lt;yegorslists@googlemail.com&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
</content>
</entry>
<entry>
<title>can: softing: Fix potential memory leak in softing_load_fw()</title>
<updated>2012-08-24T08:54:05+00:00</updated>
<author>
<name>Alexey Khoroshilov</name>
<email>khoroshilov@ispras.ru</email>
</author>
<published>2012-08-08T15:15:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=ef813c412c0cf254ddce7d922289e2d6a69960f0'/>
<id>urn:sha1:ef813c412c0cf254ddce7d922289e2d6a69960f0</id>
<content type='text'>
Do not leak memory by updating pointer with potentially NULL realloc return value.

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

Signed-off-by: Alexey Khoroshilov &lt;khoroshilov@ispras.ru&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
</content>
</entry>
<entry>
<title>net/c_can: remove conditional compilation of clk code</title>
<updated>2012-07-31T00:25:12+00:00</updated>
<author>
<name>Viresh Kumar</name>
<email>viresh.kumar@st.com</email>
</author>
<published>2012-07-30T21:39:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=2b1463ddde35a720de2fb4013057396e7f8011f0'/>
<id>urn:sha1:2b1463ddde35a720de2fb4013057396e7f8011f0</id>
<content type='text'>
With addition of dummy clk_*() calls for non CONFIG_HAVE_CLK cases in clk.h,
there is no need to have clk code enclosed in #ifdef CONFIG_HAVE_CLK, #endif
macros.

Signed-off-by: Viresh Kumar &lt;viresh.kumar@st.com&gt;
Acked-by: David S. Miller &lt;davem@davemloft.net&gt;
Cc: Bhupesh Sharma &lt;bhupesh.sharma@st.com&gt;
Cc: Russell King &lt;rmk@arm.linux.org.uk&gt;
Cc: Mike Turquette &lt;mturquette@linaro.org&gt;
Cc: Sergei Shtylyov &lt;sshtylyov@ru.mvista.com&gt;
Cc: viresh kumar &lt;viresh.linux@gmail.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>can: janz-ican3: add support for one shot mode</title>
<updated>2012-07-20T15:49:05+00:00</updated>
<author>
<name>Ira W. Snyder</name>
<email>iws@ovro.caltech.edu</email>
</author>
<published>2012-07-18T22:33:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=3b5c6b9e49f78f07ebcd34b38c1185e57a0fd9eb'/>
<id>urn:sha1:3b5c6b9e49f78f07ebcd34b38c1185e57a0fd9eb</id>
<content type='text'>
The Janz VMOD-ICAN3 hardware has support for one shot packet
transmission. This means that a packet will be attempted to be sent
once, with no automatic retries.

The SocketCAN core has a controller-wide setting for this mode:
CAN_CTRLMODE_ONE_SHOT. The Janz VMOD-ICAN3 hardware supports this flag
on a per-packet level, but the SocketCAN core does not.

Signed-off-by: Ira W. Snyder &lt;iws@ovro.caltech.edu&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
</content>
</entry>
<entry>
<title>can: janz-ican3: avoid firmware lockup caused by infinite bus error quota</title>
<updated>2012-07-20T15:49:05+00:00</updated>
<author>
<name>Ira W. Snyder</name>
<email>iws@ovro.caltech.edu</email>
</author>
<published>2012-07-18T22:33:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=30df5888e4a244093c1b403b55ef889c97824f7b'/>
<id>urn:sha1:30df5888e4a244093c1b403b55ef889c97824f7b</id>
<content type='text'>
If the bus error quota is set to infinite and the host CPU cannot keep
up, the Janz VMOD-ICAN3 firmware will stop responding to control
messages until the controller is reset.

The firmware will automatically stop sending bus error messages when the
quota is reached, and will only resume sending bus error messages when
the quota is re-set to a positive value.

This limitation is worked around by setting the bus error quota to one
message, and then re-setting the quota to one message every time a bus
error message is received. By doing this, the firmware never stops
responding to control messages. The CAN bus can be reset without a
hard-reset of the controller card.

Signed-off-by: Ira W. Snyder &lt;iws@ovro.caltech.edu&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
</content>
</entry>
</feed>
