From: "Kvaser Support" <support@kvaser.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Yegor Yefremov <yegorslists@googlemail.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Olivier Sobrie <olivier@sobrie.be>
Subject: Re: (Case 14383) SocketCAN Supported Controllers information updates
Date: Thu, 05 Jun 2014 09:18:22 +0200 [thread overview]
Message-ID: <539019be.d0a0e00a.068f.ffffc7c1@mx.google.com> (raw)
We have added the following FAQ to our website to point customers to you website for SocketCAN information:
http://www.kvaser.com/faq/linux-can-use-socketcan-kvaser-interface/
Best regards,
Troy
--
Kvaser Support
support@kvaser.com
---------------------------------------------------------------------------
-----Original Message-----
From: "Kvaser Support" <support@kvaser.com>
Reply-To: "Kvaser Support" <support@kvaser.com>
Date: Mon, 28 Apr 2014 02:24:51 +02:00
To: "Oliver Hartkopp" <socketcan@hartkopp.net>
Cc: "Yegor Yefremov" <yegorslists@googlemail.com>, "Marc Kleine-Budde" <mkl@pengutronix.de>, "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>, "Olivier Sobrie" <olivier@sobrie.be>
Subject: Re: (Case 14383) SocketCAN Supported Controllers information updates
>Looks good. Thanks for updating this information. I will let you know when we have our FAQ page up so you can comment.
>
>Best regards,
>
>Troy
>--
>Kvaser Support
>support@kvaser.com
>---------------------------------------------------------------------------
next reply other threads:[~2014-06-05 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 7:18 Kvaser Support [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-25 20:38 SocketCAN Supported Controllers information updates Oliver Hartkopp
2014-04-28 0:25 ` (Case 14383) " Kvaser Support
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=539019be.d0a0e00a.068f.ffffc7c1@mx.google.com \
--to=support@kvaser.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=olivier@sobrie.be \
--cc=socketcan@hartkopp.net \
--cc=yegorslists@googlemail.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).