Linux CAN drivers development
 help / color / mirror / Atom feed
From: ajneu <ajneu1@gmail.com>
To: linux-can@vger.kernel.org
Subject: Re: programatically determine netlink-type: can or vcan ...
Date: Thu, 23 Jun 2016 07:09:30 +0000 (UTC)	[thread overview]
Message-ID: <loom.20160623T090620-429@post.gmane.org> (raw)
In-Reply-To: loom.20160621T224622-469@post.gmane.org

ajneu <ajneu1 <at> gmail.com> writes:

> OK, it turns out that it was quite manageable, to add the desired
> functionality to libsocketcan.
> See 
> https://github.com/ajneu/libsocketcan
> https://github.com/ajneu/libsocketcan/commit/26ef

Added another commit, that adds function: device_is_up()

Why? The existing can_get_state() is limited only to can devices. It does
not work for vcan.

I hope Marc Kleine-Budde can integrate these changes into the official git.

Regards,
ajneu


  reply	other threads:[~2016-06-23  7:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 14:40 programatically determine netlink-type: can or vcan ajneu
2016-06-21 15:26 ` ajneu
2016-06-21 20:48   ` ajneu
2016-06-23  7:09     ` ajneu [this message]
2016-07-19 14:57       ` @Marc Kleine-Budde ajneu

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=loom.20160623T090620-429@post.gmane.org \
    --to=ajneu1@gmail.com \
    --cc=linux-can@vger.kernel.org \
    /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