From: David Miller <davem@davemloft.net>
To: mkl@pengutronix.de
Cc: netdev@vger.kernel.org, kernel@pengutronix.de, linux-can@vger.kernel.org
Subject: Re: pull-request: can-next 2015-03-23
Date: Mon, 23 Mar 2015 22:04:07 -0400 (EDT) [thread overview]
Message-ID: <20150323.220407.2182995151527470865.davem@davemloft.net> (raw)
In-Reply-To: <55100EA8.5010505@pengutronix.de>
From: Marc Kleine-Budde <mkl@pengutronix.de>
Date: Mon, 23 Mar 2015 14:01:28 +0100
> 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.
Pulled, thanks Marc.
prev parent reply other threads:[~2015-03-24 2:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 13:01 pull-request: can-next 2015-03-23 Marc Kleine-Budde
2015-03-24 2:04 ` David Miller [this message]
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=20150323.220407.2182995151527470865.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--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