From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kernel@pengutronix.de,
linux-can@vger.kernel.org, David Jander <david@protonic.nl>
Subject: pull-request: can-next 2015-05-06
Date: Wed, 6 May 2015 23:21:06 +0200 [thread overview]
Message-ID: <554A85C2.1020700@pengutronix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2766 bytes --]
Hello David,
this is a pull request of a seven patches for net-next/master.
Andreas Gröger contributes two patches for the janz-ican3 driver. In
the first patch, the documentation for already existing sysfs entries
is added, the second patch adds support for another module/firmware
variant. A patch by Shawn Landden makes the padding in the struct
can_frame explicit. The next 4 patches target the flexcan driver, the
first one is by David Jander adding some documentation, the reaming
three by me add more documentation and two small code cleanups.
regards,
Marc
---
The following changes since commit 239fb791d4ee194740e69fe9694f58ec404d1689:
vxlan: Correctly set flow*i_mark and flow4i_proto in route lookups (2015-05-05 19:37:54 -0400)
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.2-20150506
for you to fetch changes up to 10d089bd4b289cbe08d2565f34e030c8980682f4:
can: flexcan: replace open coded "mailbox code" by proper define (2015-05-06 22:57:27 +0200)
----------------------------------------------------------------
linux-can-next-for-4.2-20150506
----------------------------------------------------------------
Andreas Gröger (2):
can: janz-ican3: add documentation for existing sysfs entries
can: janz-ican3: add support for CAL/CANopen firmware
David Jander (1):
can: flexcan: add MB/FIFO specific column to comment table of IP versions
Marc Kleine-Budde (3):
can: flexcan: add documentation about mailbox organization
can: flexcan: rename struct flexcan_regs::crl2 -> ctrl2
can: flexcan: replace open coded "mailbox code" by proper define
Shawn Landden (1):
can.h: make padding given by gcc explicit
.../ABI/testing/sysfs-bus-pci-drivers-janz-cmodio | 8 ++
.../ABI/testing/sysfs-class-net-janz-ican3 | 19 ++++
Documentation/networking/can.txt | 3 +
drivers/mfd/janz-cmodio.c | 4 +
drivers/net/can/flexcan.c | 53 +++++----
drivers/net/can/janz-ican3.c | 125 +++++++++++++++------
include/uapi/linux/can.h | 6 +
7 files changed, 159 insertions(+), 59 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-bus-pci-drivers-janz-cmodio
create mode 100644 Documentation/ABI/testing/sysfs-class-net-janz-ican3
--
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: 801 bytes --]
next reply other threads:[~2015-05-06 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 21:21 Marc Kleine-Budde [this message]
2015-05-10 2:13 ` pull-request: can-next 2015-05-06 David Miller
-- strict thread matches above, loose matches on Subject: below --
2015-06-09 7:45 Marc Kleine-Budde
2015-06-11 4:56 ` David Miller
2015-08-20 12:13 Marc Kleine-Budde
2015-08-23 23:29 ` 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=554A85C2.1020700@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=david@protonic.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.