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-02-12
Date: Fri, 07 Mar 2014 10:45:51 +0100 [thread overview]
Message-ID: <5319954F.3080208@pengutronix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2727 bytes --]
Hello David,
this is a pull request of twelve patches for net-next/master.
Alexander Shiyan contributes two patches for the mcp251x, one making
the driver more quiet and the other one improves the compile time
coverage by removing the #ifdef CONFIG_PM_SLEEP. Then two patches for
the flexcan driver by me, one removing the #ifdef CONFIG_PM_SLEEP, too,
the other one making use of platform_get_device_id(). Another patch by
me which converts the janz-ican3 driver to use netdev_<level>(). The
remaining 7 patches are by Oliver Hartkopp, they add CAN FD support to
the netlink configuration interface.
regards,
Marc
---
The following changes since commit f3253339a47ff3690ce52e2acd95ec295f8521b3:
bonding: options handling cleanup (2014-03-06 16:08:52 -0500)
are available in the git repository at:
git://gitorious.org/linux-can/linux-can-next.git tags/linux-can-next-for-3.15-20140307
for you to fetch changes up to dd22586dec4c1444608affd83b1fedd520280ab4:
can: add bittiming check at interface open for CAN FD (2014-03-07 09:18:23 +0100)
----------------------------------------------------------------
linux-can-next-for-3.15-20140307
----------------------------------------------------------------
Alexander Shiyan (2):
can: mcp251x: Make driver more quiet
can: mcp251x: Remove #ifdef CONFIG_PM_SLEEP
Marc Kleine-Budde (3):
can: flexcan: Remove #ifdef CONFIG_PM_SLEEP
can: flexcan: make use of platform_get_device_id()
can: janz-ican3: convert dev_<level> printing to netdev_<level>
Oliver Hartkopp (7):
can: preserve skbuff protocol in can_put_echo_skb
can: only send bitrate data via netlink when available
can: move sanity check for bitrate and tq into can_get_bittiming
can: provide a separate bittiming_const parameter to bittiming functions
can: introduce the data bitrate configuration for CAN FD
can: allow to change the device mtu for CAN FD capable devices
can: add bittiming check at interface open for CAN FD
drivers/net/can/dev.c | 159 ++++++++++++++++++++++++++++++---------
drivers/net/can/flexcan.c | 10 +--
drivers/net/can/janz-ican3.c | 64 ++++++++--------
drivers/net/can/mcp251x.c | 17 ++---
include/linux/can/dev.h | 7 +-
include/uapi/linux/can/netlink.h | 3 +
6 files changed, 172 insertions(+), 88 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: 242 bytes --]
next reply other threads:[~2014-03-07 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 9:45 Marc Kleine-Budde [this message]
2014-03-07 22:10 ` pull-request: can-next 2014-02-12 David Miller
-- strict thread matches above, loose matches on Subject: below --
2014-02-12 10:15 Marc Kleine-Budde
2014-02-13 23:16 ` 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=5319954F.3080208@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).