From: Oliver Hartkopp <socketcan@hartkopp.net>
To: mkl@pengutronix.de
Cc: linux-can@vger.kernel.org
Subject: Re: pull request: can-next 2012-06-07
Date: Fri, 08 Jun 2012 17:14:56 +0200 [thread overview]
Message-ID: <4FD216F0.3050006@hartkopp.net> (raw)
In-Reply-To: <20120607.120226.1702725410216999138.davem@davemloft.net>
On 07.06.2012 21:02, David Miller wrote:
> From: Marc Kleine-Budde <mkl@pengutronix.de>
> Date: Thu, 07 Jun 2012 10:14:11 +0200
>
>> here two patches for net-next, by AnilKumar Ch, they add support for
>> Bosch's d_can hardware to the existing c_can driver.
>
> Pulled, thanks.
Marc,
can you please update the can-next tree, so that i can prepare the patch
series for CAN FD support for this development cycle?
Thanks,
Oliver
next prev parent reply other threads:[~2012-06-08 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 8:14 pull request: can-next 2012-06-07 Marc Kleine-Budde
2012-06-07 19:02 ` David Miller
2012-06-08 15:14 ` Oliver Hartkopp [this message]
2012-06-10 17:24 ` Marc Kleine-Budde
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=4FD216F0.3050006@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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).