From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: pull-request: can-next 2014-12-07
Date: Mon, 08 Dec 2014 00:33:23 +0100 [thread overview]
Message-ID: <5484E3C3.5030205@pengutronix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2697 bytes --]
Hello David,
this is a pull request of 8 patches for net-next/master.
Andri Yngvason contributes 4 patches in which the CAN state change
handling is consolidated and unified among the sja1000, mscan and
flexcan driver. The three patches by Jeremiah Mahler fix spelling
mistakes and eliminate the banner[] variable in various parts. And a
patch by me that switches on sparse endianess checking by default.
Marc
---
The following changes since commit 8d0c4697534a739725e429ff062dea393d8860d1:
Merge branch 'ebpf-next' (2014-12-05 21:47:48 -0800)
are available in the git repository at:
git://gitorious.org/linux-can/linux-can-next.git tags/linux-can-next-for-3.19-20141207
for you to fetch changes up to 71a3aedce6b37318d0e38676681dff179ec42874:
can: flexcan: Consolidate and unify state change handling (2014-12-07 21:22:10 +0100)
----------------------------------------------------------------
linux-can-next-for-3.19-20141207
----------------------------------------------------------------
Andri Yngvason (4):
can: dev: Consolidate and unify state change handling
can: sja1000: Consolidate and unify state change handling
can: mscan: Consolidate and unify state change handling
can: flexcan: Consolidate and unify state change handling
Jeremiah Mahler (3):
can: eliminate banner[] variable and switch to pr_info()
can: slcan/vcan: eliminate banner[] variable, switch to pr_info()
can: fix spelling errors
Marc Kleine-Budde (1):
can: Enable -D__CHECK_ENDIAN__ for sparse by default
drivers/net/can/Makefile | 3 +-
drivers/net/can/cc770/cc770.c | 2 +-
drivers/net/can/dev.c | 78 +++++++++++++++++++++++++++++
drivers/net/can/flexcan.c | 101 +++++++-------------------------------
drivers/net/can/mscan/mscan.c | 48 ++++++------------
drivers/net/can/sja1000/sja1000.c | 51 +++++++++----------
drivers/net/can/slcan.c | 7 +--
drivers/net/can/vcan.c | 5 +-
include/linux/can/dev.h | 3 ++
include/uapi/linux/can/error.h | 1 +
net/can/af_can.c | 7 +--
net/can/bcm.c | 16 +++---
net/can/gw.c | 2 +-
net/can/raw.c | 4 +-
14 files changed, 154 insertions(+), 174 deletions(-)
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-12-07 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 23:33 Marc Kleine-Budde [this message]
2014-12-09 21:49 ` pull-request: can-next 2014-12-07 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=5484E3C3.5030205@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).