From: David Miller <davem@davemloft.net>
To: erik.hugne@ericsson.com
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
jon.maloy@ericsson.com, maloy@donjonn.com,
ying.xue@windriver.com, paul.gortmaker@windriver.com,
richard.alpe@ericsson.com
Subject: Re: [PATCH net-next v2 0/2] tipc: add support for link state subscriptions
Date: Sat, 26 Apr 2014 12:13:55 -0400 (EDT) [thread overview]
Message-ID: <20140426.121355.2287323378064995557.davem@davemloft.net> (raw)
In-Reply-To: <1398349607-16012-1-git-send-email-erik.hugne@ericsson.com>
From: <erik.hugne@ericsson.com>
Date: Thu, 24 Apr 2014 16:26:45 +0200
> From: Erik Hugne <erik.hugne@ericsson.com>
>
> Low level topology information like TIPC link up/down is useful for
> applications like teamd to make smarter failover decisions in a
> HA cluster environment. Fetching logical link names through an ioctl
> may hurt the eyes of some. Suggestions for a more elegant way of doing
> this would be appreciated in that case. :)
>
> v2:
> -Properly based on net-next
> -Off-list comments from Billie Alsup:
> -Add a string length parameter to tipc_node_get_linkname
> -Use TIPC_MAX_LINK_NAME definition instead of hardcoded
> value in tipc_sioc_ln_req linkname
Series applied, thanks.
prev parent reply other threads:[~2014-04-26 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 14:26 [PATCH net-next v2 0/2] tipc: add support for link state subscriptions erik.hugne
2014-04-24 14:26 ` [PATCH net-next v2 1/2] " erik.hugne
2014-04-24 14:26 ` [PATCH net-next v2 2/2] tipc: add ioctl to fetch link names erik.hugne
2014-04-26 16:13 ` David Miller [this message]
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=20140426.121355.2287323378064995557.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=erik.hugne@ericsson.com \
--cc=jon.maloy@ericsson.com \
--cc=maloy@donjonn.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=richard.alpe@ericsson.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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).