From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Michal Simek <michal.simek@xilinx.com>
Cc: Soren Brinkmann <soren.brinkmann@xilinx.com>,
Kedareswara rao Appana <appanad@xilinx.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Xilinx Zynq CAN driver
Date: Fri, 03 Jan 2014 15:10:54 +0100 [thread overview]
Message-ID: <52C6C4EE.1010509@hartkopp.net> (raw)
In-Reply-To: <15ba5e14-8553-4b02-94b6-91b1a8e93691@DB8EHSMHS025.ehs.local>
On 03.01.2014 14:40, Michal Simek wrote:
>
> We are in process of validation of our drivers and they will be send to mainline
> soon. I was in touch with Marc regarding can driver testing which we need to do.
>
Great!
Thanks in advance for your contribution.
Best regards,
Oliver
prev parent reply other threads:[~2014-01-03 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 11:26 Xilinx Zynq CAN driver Oliver Hartkopp
2014-01-03 13:40 ` Michal Simek
2014-01-03 14:10 ` Oliver Hartkopp [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=52C6C4EE.1010509@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=appanad@xilinx.com \
--cc=linux-can@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=soren.brinkmann@xilinx.com \
/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).