From: Richard Alpe <richard.alpe@ericsson•com>
To: Pavel Simerda <psimerda@redhat•com>,
Stephen Hemminger <stephen@networkplumber•org>
Cc: netdev@vger•kernel.org, tipc-discussion@lists•sourceforge.net
Subject: Re: [PATCH iproute2] tipc: introduce TIPC configuration tool
Date: Thu, 4 Jun 2015 13:40:47 +0200 [thread overview]
Message-ID: <5570393F.9060401@ericsson.com> (raw)
In-Reply-To: <1689829731.5883859.1433413415372.JavaMail.zimbra@redhat.com>
On 2015-06-04 12:23, Pavel Simerda wrote:
> ----- Original Message -----
>> From: "Stephen Hemminger" <stephen@networkplumber•org>
>> To: "richard alpe" <richard.alpe@ericsson•com>
>> Cc: netdev@vger•kernel.org, tipc-discussion@lists•sourceforge.net
>> Sent: Thursday, May 21, 2015 11:43:40 PM
>> Subject: Re: [PATCH iproute2] tipc: introduce TIPC configuration tool
>>
>> On Thu, 7 May 2015 15:07:35 +0200
>> <richard.alpe@ericsson•com> wrote:
>>
>>> From: Richard Alpe <richard.alpe@ericsson•com>
>>>
>>> This is the new tipc tool that utilizes the relativly new TIPC netlink API
>>> in
>>> the kernel. Introducing this tool into iproute2 has been discussed
>>> previously.
>>>
>>> For more information about the design decisions of this tool, see the
>>> README
>>> file.
>>>
>>> There isn't yet a manpage for the this tool. I will start to write one once
>>> I
>>> submitted this for review.
>>>
>>> Richard Alpe (1):
>>> tipc: add new TIPC configuration tool
>>
>> I went ahead and merged this.
>> It does add dependency on libmnl which the distribution maintainers will have
>> to add to their stuff.
>
> Does the new dependency suggest the whole iproute2 is moving to libmnl?
That is what I was told and the reason I wrote "tipc" based on libmnl.
Regards
Richard
> Or is
> there a good reason to use an external netlink library as well as an internal one?
>
> Cheers,
>
> Pavel
>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe netdev" in
>> the body of a message to majordomo@vger•kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
------------------------------------------------------------------------------
next prev parent reply other threads:[~2015-06-04 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 13:07 [PATCH iproute2] tipc: introduce TIPC configuration tool richard.alpe
2015-05-07 13:07 ` [PATCH iproute2] tipc: add new " richard.alpe
2015-05-21 21:43 ` [PATCH iproute2] tipc: introduce " Stephen Hemminger
2015-06-04 10:23 ` Pavel Simerda
2015-06-04 11:40 ` Richard Alpe [this message]
2015-06-04 17:30 ` Pavel Simerda
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=5570393F.9060401@ericsson.com \
--to=richard.alpe@ericsson$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=psimerda@redhat$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
--cc=tipc-discussion@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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