netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 2015-03-23
Date: Mon, 23 Mar 2015 14:01:28 +0100	[thread overview]
Message-ID: <55100EA8.5010505@pengutronix.de> (raw)

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

Hello David,

this is a pull request of 6 patches for net-next/master.

A patch by Florian Westphal, converts the skb->destructor to use
sock_efree() instead of own destructor. Ahmed S. Darwish's patch
converts the kvaser_usb driver to use unregister_candev(). A patch by
me removes a return from a void function in the m_can driver. Yegor
Yefremov contributes a patch for combined rx/tx LED trigger support. A
sparse warning in the esd_usb2 driver was fixes by Thomas Körper. Ben
Dooks converts the at91_can driver to use endian agnostic IO accessors.

Marc

---

The following changes since commit 8f2ddaac302a8ca364cb04efb19cd3b5cd058910:

  netlink: Remove netlink_compare_arg.trailer (2015-03-21 00:16:39 -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.1-20150323

for you to fetch changes up to af9bfbdab8f1c5a4b51a45aaab4cfbcc318b8ae2:

  can: at91_can: use endian agnostic IO accessors (2015-03-22 23:50:12 +0100)

----------------------------------------------------------------
linux-can-next-for-4.1-20150323

----------------------------------------------------------------
Ahmed S. Darwish (1):
      can: kvaser_usb: Use can-dev unregistration mechanism

Ben Dooks (1):
      can: at91_can: use endian agnostic IO accessors

Florian Westphal (1):
      can: use sock_efree instead of own destructor

Marc Kleine-Budde (1):
      can: m_cam: m_can_fifo_write(): remove return from void function

Thomas Körper (1):
      can: esd_usb2: Fix sparse warnings

Yegor Yefremov (1):
      can: add combined rx/tx LED trigger support

 drivers/net/can/at91_can.c       |  4 ++--
 drivers/net/can/led.c            | 22 +++++++++++++++++++---
 drivers/net/can/m_can/m_can.c    |  4 ++--
 drivers/net/can/usb/esd_usb2.c   |  4 ++--
 drivers/net/can/usb/kvaser_usb.c |  2 +-
 include/linux/can/dev.h          |  2 ++
 include/linux/can/led.h          |  6 ++++--
 include/linux/can/skb.h          |  7 +------
 8 files changed, 33 insertions(+), 18 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 --]

             reply	other threads:[~2015-03-23 13:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 13:01 Marc Kleine-Budde [this message]
2015-03-24  2:04 ` pull-request: can-next 2015-03-23 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=55100EA8.5010505@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).