linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: davem@davemloft.net
Cc: Linux Netdev List <netdev@vger.kernel.org>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: pull-request: can-next 2012-06-19
Date: Tue, 19 Jun 2012 22:01:56 +0200	[thread overview]
Message-ID: <4FE0DAB4.6080400@pengutronix.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 2556 bytes --]

Hello David,

here is our second pull request for net-next. In this series Federico
Vaga adds a pci driver for c_can/d_can hardware using the existing
generic c_can driver. The remaining 6 patches are by Oliver Hartkopp.
He adds CANFD support to the CAN stack while keeping binary
compatibility for existing applications. CANFD is an extension to the
existing CAN standard, it allows longer CAN frames and/or higher data
rates. There's no real hardware available yet, but this series adds
CANFD support to the vcan driver.

regards,
Marc

---

The following changes since commit b31525d16b50fe0eb33545afbc0be1a03f2896e3:

  net: lpc_eth: Driver cleanup (2012-06-19 00:27:03 -0700)

are available in the git repository at:

  git://gitorious.org/linux-can/linux-can-next.git master

for you to fetch changes up to ea53fe0c667ad3cae61d4d71d2be41908ac5c0a4:

  canfd: update documentation according to CAN FD extensions (2012-06-19 21:40:26 +0200)

----------------------------------------------------------------
Federico Vaga (1):
      c_can_pci: generic module for C_CAN/D_CAN on PCI

Oliver Hartkopp (6):
      canfd: add new data structures and constants
      canfd: add support for CAN FD in PF_CAN core
      canfd: add support for CAN FD in CAN_RAW sockets
      candev: add/update helpers for CAN FD
      vcan: add CAN FD support
      canfd: update documentation according to CAN FD extensions

 Documentation/networking/can.txt  |  154 ++++++++++++++++++++++++++++--
 drivers/net/can/c_can/Kconfig     |    7 ++
 drivers/net/can/c_can/Makefile    |    1 +
 drivers/net/can/c_can/c_can_pci.c |  236 ++++++++++++++++++++++++++++++++++++++++++++++
 drivers/net/can/dev.c             |   35 ++++++-
 drivers/net/can/vcan.c            |   27 ++++--
 include/linux/can.h               |   59 +++++++++++-
 include/linux/can/core.h          |    4 +-
 include/linux/can/dev.h           |   33 +++++--
 include/linux/can/raw.h           |    3 +-
 include/linux/if_ether.h          |    3 +-
 net/can/af_can.c                  |  116 +++++++++++++++++------
 net/can/raw.c                     |   50 +++++++++-
 13 files changed, 664 insertions(+), 64 deletions(-)
 create mode 100644 drivers/net/can/c_can/c_can_pci.c


-- 
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: 262 bytes --]

             reply	other threads:[~2012-06-19 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19 20:01 Marc Kleine-Budde [this message]
2012-06-19 21:48 ` pull-request: can-next 2012-06-19 David Miller
2012-06-19 21:59   ` David Miller
2012-06-19 22:01     ` 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=4FE0DAB4.6080400@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=davem@davemloft.net \
    --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).