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-04
Date: Wed, 04 Mar 2015 10:42:13 +0100 [thread overview]
Message-ID: <54F6D375.8060301@pengutronix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]
Hello David,
this is a pull request of 3 patches for net-next/master.
Aaron Wu contributes three patches for the blackfin can driver, which
cleans up the driver and makes use of more platform independent code.
Marc
---
The following changes since commit 2f56f6be47dbc6883e28107edfe2f9f98f4d5a24:
bridge: fix bridge netlink RCU usage (2015-03-04 00:20:22 -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.1-20150304
for you to fetch changes up to 400aff5da5f2c202e8ff2679005981583234df54:
bfin_can: Merge header file from arch dependent location (2015-03-04 09:52:49 +0100)
----------------------------------------------------------------
linux-can-next-for-4.1-20150304
----------------------------------------------------------------
Aaron Wu (3):
bfin_can: rewrite the blackfin style of read/write to common ones
bfin_can: introduce ioremap to comply to archs with MMU
bfin_can: Merge header file from arch dependent location
drivers/net/can/bfin_can.c | 258 +++++++++++++++++++++++++++++++--------------
1 file changed, 177 insertions(+), 81 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 --]
next reply other threads:[~2015-03-04 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 9:42 Marc Kleine-Budde [this message]
2015-03-04 21:41 ` pull-request: can-next 2015-03-04 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=54F6D375.8060301@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).