From: "Max S." <max@schneidersoft.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Thanks! Re: pull-request: can-next 2014-05-19
Date: Sat, 31 May 2014 15:38:49 +0000 [thread overview]
Message-ID: <1401550729.32359.16.camel@blackbox> (raw)
In-Reply-To: <5379B6CE.60004@pengutronix.de>
Hello all.
Thanks allot for all the help on getting this driver this far.
I've got two tethered units I'm be willing to give away. So if any of
the people who helped me with this project are interested, send me an
address to ship to. If you are interested, please make sure you have a
use for the device :)
Again thanks to all the people involved. Especially Marc, Oliver, and
Wolfgang.
Regards,
Maximilian Schneider.
On Mon, 2014-05-19 at 09:46 +0200, Marc Kleine-Budde wrote:
> Hello David,
>
> this is a pull request of 13 patches for net-next/master.
>
> A patch by Dan Carpenter fixes a coccinelle warning in the mcp251x
> driver. Jean Delvare contributes three patches to tightening the
> Kconfig dependencies for some drivers. Then come three patches by Pavel
> Machek that improve the c_can driver support on the socfpga platform.
> Sergei Shtylyov's patch brings support for the CAN hardware found on
> Renesas R-Car CAN controllers. Four patches by Oliver Hartkopp, the
> first cleans up the guard macros in the CAN headers the other three
> improve the EFF frame filtering. Maximilian Schneider's patch adds
> support for the GS_USB CAN devices.
>
> Marc
>
prev parent reply other threads:[~2014-05-31 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 7:46 pull-request: can-next 2014-05-19 Marc Kleine-Budde
2014-05-21 6:01 ` David Miller
2014-05-31 15:38 ` Max S. [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=1401550729.32359.16.camel@blackbox \
--to=max@schneidersoft.net \
--cc=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).