From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: pull-request: can 2015-07-12
Date: Sun, 12 Jul 2015 21:18:03 +0200 [thread overview]
Message-ID: <1436728691-1145-1-git-send-email-mkl@pengutronix.de> (raw)
Hello David,
this is a pull request of 8 patchs for net/master.
Sergei Shtylyov contributes 5 patches for the rcar_can driver, fixing the IRQ
check and several info and error messages. There are two patches by J.D.
Schroeder and Roger Quadros for the c_can driver and dra7x-evm device tree,
which precent a glitch in the DCAN1 pinmux. Oliver Hartkopp provides a better
approach to make the CAN skbs unique, the timestamp is replaced by a counter.
regards,
Marc
---
The following changes since commit 2ee94014d9bd3868b1c0d17405f96d63bec83f28:
net: switchdev: don't abort unsupported operations (2015-07-11 21:29:55 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git tags/linux-can-fixes-for-4.2-20150712
for you to fetch changes up to d3b58c47d330de8c29898fe9746f7530408f8a59:
can: replace timestamp as unique skb attribute (2015-07-12 21:13:22 +0200)
----------------------------------------------------------------
linux-can-fixes-for-4.2-20150712
----------------------------------------------------------------
J.D. Schroeder (1):
can: c_can: Fix default pinmux glitch at init
Oliver Hartkopp (1):
can: replace timestamp as unique skb attribute
Roger Quadros (1):
ARM: dts: dra7x-evm: Prevent glitch on DCAN1 pinmux
Sergei Shtylyov (5):
can: rcar_can: fix IRQ check
can: rcar_can: print signed IRQ #
can: rcar_can: fix typo in error message
can: rcar_can: print request_irq() error code
can: rcar_can: unify error messages
arch/arm/boot/dts/dra7-evm.dts | 5 +++--
arch/arm/boot/dts/dra72-evm.dts | 5 +++--
drivers/net/can/c_can/c_can.c | 10 ++++++++--
drivers/net/can/dev.c | 7 ++-----
drivers/net/can/rcar_can.c | 16 ++++++++++------
drivers/net/can/slcan.c | 2 +-
drivers/net/can/vcan.c | 3 ---
include/linux/can/skb.h | 2 ++
net/can/af_can.c | 12 +++++++-----
net/can/bcm.c | 2 ++
net/can/raw.c | 7 ++++---
11 files changed, 42 insertions(+), 29 deletions(-)
next reply other threads:[~2015-07-12 19:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 19:18 Marc Kleine-Budde [this message]
2015-07-12 19:18 ` [PATCH 1/8] can: rcar_can: fix IRQ check Marc Kleine-Budde
2015-07-12 19:18 ` [PATCH 2/8] can: rcar_can: print signed IRQ # Marc Kleine-Budde
2015-07-12 19:18 ` [PATCH 3/8] can: rcar_can: fix typo in error message Marc Kleine-Budde
2015-07-12 19:18 ` [PATCH 4/8] can: rcar_can: print request_irq() error code Marc Kleine-Budde
2015-07-12 19:18 ` [PATCH 5/8] can: rcar_can: unify error messages Marc Kleine-Budde
2015-07-12 19:18 ` [PATCH 6/8] can: c_can: Fix default pinmux glitch at init Marc Kleine-Budde
2015-07-12 19:18 ` [PATCH 7/8] ARM: dts: dra7x-evm: Prevent glitch on DCAN1 pinmux Marc Kleine-Budde
2015-07-12 19:18 ` [PATCH 8/8] can: replace timestamp as unique skb attribute Marc Kleine-Budde
2015-07-27 18:34 ` Oliver Hartkopp
2015-08-04 19:18 ` Greg KH
2015-07-13 5:24 ` pull-request: can 2015-07-12 David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1436728691-1145-1-git-send-email-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).