From: David Miller <davem@davemloft.net>
To: mkl@pengutronix.de
Cc: netdev@vger.kernel.org, linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: Re: pull-request: can-next 2013-12-17
Date: Thu, 19 Dec 2013 15:13:49 -0500 (EST) [thread overview]
Message-ID: <20131219.151349.190638879390015561.davem@davemloft.net> (raw)
In-Reply-To: <52B02F1F.6020702@pengutronix.de>
From: Marc Kleine-Budde <mkl@pengutronix.de>
Date: Tue, 17 Dec 2013 12:01:51 +0100
> this is a pull request of four patches for net-next/master.
>
> There is one patch by Markus Pargmann, which speeds up the c_can
> driver, a patch by John Whitmore which updates the in tree
> documentation. A patch by Jeff Kirsher which replaces the FSF's address
> by a link and a patch by Alexander Shiyan which converts the mcp251x
> driver to make use of managed resources.
Pulled, thanks Marc.
prev parent reply other threads:[~2013-12-19 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 11:01 pull-request: can-next 2013-12-17 Marc Kleine-Budde
2013-12-19 20:13 ` 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=20131219.151349.190638879390015561.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;
as well as URLs for NNTP newsgroup(s).