From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Wolfgang Grandegger <wg@grandegger.com>,
Stephane Grosjean <s.grosjean@peak-system.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Is there any way of getting the CAN interfaces list, from any C program?
Date: Thu, 25 Apr 2013 11:23:42 +0200 [thread overview]
Message-ID: <5178F61E.9040506@pengutronix.de> (raw)
In-Reply-To: <20130425091421.GD448@vandijck-laurijssen.be>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
On 04/25/2013 11:14 AM, Kurt Van Dijck wrote:
> I was just thinking that it has not that much to do with CAN altogether,
> and may deserve a seperate git tree.
>
> I'm just rewriting the code a bit to work without callback, and be more like
> if_nameindex().
Would be cool if the functions follows the same semantics as
if_nameindex(), i.e. it could be named canif_nameindex() and just return
CAN interfaces, not all.
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: 263 bytes --]
next prev parent reply other threads:[~2013-04-25 9:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 19:35 [RFC PATCH v2] can: sja1000: use common prefix for all sja1000 defines Oliver Hartkopp
2013-04-16 10:40 ` Marc Kleine-Budde
2013-04-24 9:06 ` Is there any way of getting the CAN interfaces list, from any C program? Stephane Grosjean
2013-04-24 14:49 ` Kurt Van Dijck
2013-04-25 6:41 ` Wolfgang Grandegger
2013-04-25 7:07 ` Marc Kleine-Budde
2013-04-25 7:35 ` Marc Kleine-Budde
2013-04-25 9:15 ` Kurt Van Dijck
2013-04-25 9:20 ` Marc Kleine-Budde
2013-04-25 7:24 ` Kurt Van Dijck
2013-04-25 7:43 ` Wolfgang Grandegger
2013-04-25 9:14 ` Kurt Van Dijck
2013-04-25 9:23 ` Marc Kleine-Budde [this message]
2013-04-25 9:42 ` Kurt Van Dijck
2013-04-25 21:08 ` Kurt Van Dijck
2013-04-24 21:02 ` François
2013-04-24 21:27 ` Marc Kleine-Budde
2013-04-25 8:04 ` 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=5178F61E.9040506@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=s.grosjean@peak-system.com \
--cc=wg@grandegger.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).