From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Yegor Yefremov <yegorslists@googlemail.com>,
Kvaser Support <support@kvaser.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Olivier Sobrie <olivier@sobrie.be>
Subject: Re: (Case 14359) Kvaser socketCAN support
Date: Thu, 24 Apr 2014 14:01:03 +0200 [thread overview]
Message-ID: <5358FCFF.9020604@hartkopp.net> (raw)
In-Reply-To: <5358D731.9000908@pengutronix.de>
On 24.04.2014 11:19, Marc Kleine-Budde wrote:
> On 04/24/2014 09:46 AM, Yegor Yefremov wrote:
>> What about making a table with following columns:
>>
>> 1. driver module name
>> 2. supported devices
>> 3. kernel version, where all these devices are supported
>>
>> *alternative variant*
>>
>> 1. device name
>> 2. related driver module name
>> 3. kernel version
>
> ^^^ I think this is the most useful variant.
Yep!
If possible I would like to add the Vendor too:
1. Vendor (with URL to the Vendor)
2. device name (with URL to the Product if possible)
3. related driver module name
4. Kconfig option: CONFIG_CAN CONFIG_CAN_DEV CONFIG_SJA1000 CONFIG_EMS_PCMCIA
5. since kernel version (or "out-of-tree")
6. Remarks
Point 4. might probably be too much ...
As elinux.org uses the same Wiki system, i would suggest to
have a sorted table to be able to sort by Vendor / device name / Kernel version
See:
http://en.wikipedia.org/wiki/Help:Table#Sorting_and_collapsing
Btw. the DE example looks better
http://de.wikipedia.org/wiki/Hilfe:Tabellen#Sortierbare_Tabelle
Regards,
Oliver
ps. My account creation at elinux.org still waits for approval ...
next prev parent reply other threads:[~2014-04-24 12:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f0331cq3H1VPknv.RZmta@smtp.rzone.de>
2014-04-21 17:48 ` Kvaser socketCAN support Oliver Hartkopp
2014-04-22 0:40 ` (Case 14359) " Kvaser Support
2014-04-22 5:54 ` Yegor Yefremov
2014-04-23 7:38 ` Kvaser Support
2014-04-23 7:48 ` Yegor Yefremov
2014-04-23 16:19 ` Kvaser Support
2014-04-24 7:46 ` Yegor Yefremov
2014-04-24 9:19 ` Marc Kleine-Budde
2014-04-24 12:01 ` Oliver Hartkopp [this message]
2014-04-24 12:06 ` Marc Kleine-Budde
2014-04-24 12:34 ` Yegor Yefremov
2014-04-24 18:56 ` Oliver Hartkopp
2014-04-24 19:29 ` Yegor Yefremov
2014-04-24 22:12 ` Kvaser Support
2014-04-25 20:38 ` SocketCAN Supported Controllers information updates Oliver Hartkopp
2014-04-28 0:25 ` (Case 14383) " Kvaser Support
2014-04-27 17:41 ` elinux wiki Kurt Van Dijck
[not found] ` <r049e3q3UHfiSQJ.RZmta@smtp.rzone.de>
2014-05-01 8:56 ` Kvaser socketCAN support Oliver Hartkopp
[not found] ` <R0595dq41EVg2BS.RZmta@smtp.rzone.de>
2014-05-01 16:24 ` Oliver Hartkopp
[not found] ` <6073ccq41HkW3ar.RZmta@smtp.rzone.de>
2014-05-01 18:46 ` Oliver Hartkopp
[not found] ` <53628879.751e8c0a.6be4.ffffc061SMTPIN_ADDED_MISSING@mx.google.com>
2014-05-01 20:46 ` Olivier Sobrie
[not found] ` <5363a95a.e3208c0a.bc54.574dSMTPIN_ADDED_MISSING@mx.google.com>
2014-05-03 13:18 ` Olivier Sobrie
2014-05-04 6:00 ` (Case 14420) " Kvaser Support
2014-05-04 20:14 ` Olivier Sobrie
2014-05-04 21:23 ` Kvaser Support
2014-05-11 20:34 ` Olivier Sobrie
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=5358FCFF.9020604@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=olivier@sobrie.be \
--cc=support@kvaser.com \
--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).