From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
"Christopher R. Baker" <cbaker@rec.ri.cmu.edu>
Cc: linux-can@vger.kernel.org
Subject: Re: Populating netdev::dev_id for udev discrimination
Date: Tue, 11 Mar 2014 20:45:56 +0100 [thread overview]
Message-ID: <531F67F4.20907@pengutronix.de> (raw)
In-Reply-To: <531F66F8.2060506@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
On 03/11/2014 08:41 PM, Oliver Hartkopp wrote:
>>> FYI:
>>>
>>> Tested with PEAK PCAN USB pro and EMS PCMCIA (both with two channels) and the
>>> dev_id works like expected (first channel dev_id = 0x0, second channel 0x1).
>>
>> Can I add your Tested-by for the Peak and the EMS?
>>
>
> Oh, yes.
>
> At least for these two adapters I checked it myself.
I've added:
Tested-by: Oliver Hartkopp <socketcan@hartkopp.net> [PEAK PCAN-USB pro and EMS PCMCIA]
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 242 bytes --]
next prev parent reply other threads:[~2014-03-11 19:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-08 16:00 Populating netdev::dev_id for udev discrimination Christopher R. Baker
2014-03-09 19:05 ` Marc Kleine-Budde
2014-03-09 23:32 ` Christopher R. Baker
2014-03-10 7:43 ` Oliver Hartkopp
2014-03-10 10:46 ` Kurt Van Dijck
2014-03-10 11:01 ` Marc Kleine-Budde
2014-03-10 12:18 ` Oliver Hartkopp
2014-03-11 19:08 ` Marc Kleine-Budde
2014-03-11 19:41 ` Oliver Hartkopp
2014-03-11 19:45 ` Marc Kleine-Budde [this message]
2014-03-10 12:18 ` Kurt Van Dijck
2014-03-10 12:15 ` Oliver Hartkopp
2014-03-10 12:52 ` Kurt Van Dijck
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=531F67F4.20907@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=cbaker@rec.ri.cmu.edu \
--cc=linux-can@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.