From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Alex Layton <alex@layton.in>,
linux-can <linux-can@vger.kernel.org>,
Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
Subject: Re: can-j1939: semantics question
Date: Wed, 11 Nov 2015 21:49:14 +0100 [thread overview]
Message-ID: <5643A9CA.8060509@hartkopp.net> (raw)
In-Reply-To: <20151111195255.GB23275@airbook.vandijck-laurijssen.be>
On 11.11.2015 20:52, Kurt Van Dijck wrote:
> I eventually got into investigating the necessary changes to drop
> iproute2 from can-j1939.
> We somewhat agreed that opening a can-j1939 socket and binding
> to a CAN interface should activate can-j1939 processing for that
> interface.
> But how about deactivation?
> Should the last can-j1939 socket on a CAN iface deactivate can-j1939 for
> that iface when that socket closes?
At least this sounds like some kind of natural behaviour.
What would be the other option?
Would you still monitor address claiming inside the kernel without doing
anything else?
Or is the address claiming in user space the last application that closes the
last socket anyway??
Regards,
Oliver
next prev parent reply other threads:[~2015-11-11 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 19:52 can-j1939: semantics question Kurt Van Dijck
2015-11-11 20:49 ` Oliver Hartkopp [this message]
2015-11-12 8:39 ` 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=5643A9CA.8060509@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=alex@layton.in \
--cc=dev.kurt@vandijck-laurijssen.be \
--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 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.