From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: pull-request: can-next 2016-02-20
Date: Sat, 20 Feb 2016 15:09:42 +0100 [thread overview]
Message-ID: <56C873A6.2000102@pengutronix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2664 bytes --]
Hello David,
this is a pull request of 9 patch for net-next/master.
The first 3 patches are from Damien Riegel, they add support for
Technologic Systems IP core to tje sja100 driver. The next patches 6 by
Marek Vasut (including one my me) first clean sort the CAN driver's
Kconfig and Makefiles and then add support for the IFI CANFD IP core.
Marc
---
The following changes since commit 80c804bfc487c6df783c258b9034b9d81c34f7a0:
Merge branch 'bpf-get-stackid' (2016-02-20 00:21:44 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git tags/linux-can-next-for-4.6-20160220
for you to fetch changes up to 0c4d9c94a1303008b32079991360cea7ab849ef3:
can: ifi: Add IFI CANFD IP support (2016-02-20 14:56:15 +0100)
----------------------------------------------------------------
linux-can-next-for-4.6-20160220
----------------------------------------------------------------
Damien Riegel (3):
can: sja1000: of: add per-compatible init hook
can: sja1000: add documentation for Technologic Systems version
can: sja1000: of: add compatibility with Technologic Systems version
Marc Kleine-Budde (1):
can: Kconfig: sort drivers alphabetically
Marek Vasut (5):
can: Kconfig: Sort the Kconfig includes
can: Makefile: Sort the Makefile
of: Add vendor prefix for I/F/I
can: ifi: Add DT bindings for ifi,canfd
can: ifi: Add IFI CANFD IP support
.../devicetree/bindings/net/can/ifi_canfd.txt | 15 +
.../devicetree/bindings/net/can/sja1000.txt | 3 +-
.../devicetree/bindings/vendor-prefixes.txt | 1 +
drivers/net/can/Kconfig | 64 +-
drivers/net/can/Makefile | 17 +-
drivers/net/can/ifi_canfd/Kconfig | 8 +
drivers/net/can/ifi_canfd/Makefile | 5 +
drivers/net/can/ifi_canfd/ifi_canfd.c | 917 +++++++++++++++++++++
drivers/net/can/sja1000/sja1000_platform.c | 87 +-
9 files changed, 1064 insertions(+), 53 deletions(-)
create mode 100644 Documentation/devicetree/bindings/net/can/ifi_canfd.txt
create mode 100644 drivers/net/can/ifi_canfd/Kconfig
create mode 100644 drivers/net/can/ifi_canfd/Makefile
create mode 100644 drivers/net/can/ifi_canfd/ifi_canfd.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: 455 bytes --]
next reply other threads:[~2016-02-20 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 14:09 Marc Kleine-Budde [this message]
2016-02-22 3:39 ` pull-request: can-next 2016-02-20 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=56C873A6.2000102@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).