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 2014-08-20
Date: Fri, 22 Aug 2014 19:43:06 -0700 (PDT) [thread overview]
Message-ID: <20140822.194306.1213839822576773356.davem@davemloft.net> (raw)
In-Reply-To: <53F4B580.3030802@pengutronix.de>
From: Marc Kleine-Budde <mkl@pengutronix.de>
Date: Wed, 20 Aug 2014 16:49:36 +0200
> There is one patch by Wolfram Sang to clean up the build system.
> Two patches by Stefan Agner that add vf610 support to the flexcan
> driver. Dong Aisheng add support for bosch's m_can core, which is found
> in the new freescale ARM SoCs. Sergei Shtylyov improves the rcar_can
> driver by supporting all input clocks and adding device tree support.
> The next patch is a small cleanup for the bit rate calculation function
> by Lad, Prabhakar. And finally a patch by Himangi Saraogi, which
> converts the mcp251x driver to use dmam_alloc_coherent.
Pulled, thanks Marc.
prev parent reply other threads:[~2014-08-23 2:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 14:49 pull-request: can-next 2014-08-20 Marc Kleine-Budde
2014-08-23 2:43 ` 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=20140822.194306.1213839822576773356.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).