netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>,
	Andrea Claudi <aclaudi@redhat.com>, Ying Xu <yinxu@redhat.com>
Subject: Re: [PATCH iproute2] lib: move rtnl_echo_talk from libnetlink to utils
Date: Fri, 14 Jul 2023 11:28:33 +0800	[thread overview]
Message-ID: <ZLDA4dT+pF6AeTP3@Laptop-X1> (raw)
In-Reply-To: <20230713152846.5735066e@hermes.local>

On Thu, Jul 13, 2023 at 03:28:46PM -0700, Stephen Hemminger wrote:
> On Wed, 12 Jul 2023 11:11:46 +0800
> Hangbin Liu <liuhangbin@gmail.com> wrote:
> 
> > > compatibility if an application links with it.  Collect2 should be
> > > using a supported library like libmnl instea.  
> > 
> > It's not about compatibility. If an application linked with netlink.a, the
> > build will failed. e.g. 
> 
> Applications that link with libnetlink.a do so at their own risk.
> It is not guaranteed to be a standalone library.
> If it worked be for, that was by accident not intention.
> 
> The reason libnetlink.a is not supported is that the same reason that
> kernel API's are not fixed. Also, there is no test suite for just libnetlink.

Thanks for the explain.

Regards
Hangbin

      reply	other threads:[~2023-07-14  3:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11  7:31 [PATCH iproute2] lib: move rtnl_echo_talk from libnetlink to utils Hangbin Liu
2023-07-11 16:00 ` Stephen Hemminger
2023-07-12  3:11   ` Hangbin Liu
2023-07-13 22:28     ` Stephen Hemminger
2023-07-14  3:28       ` Hangbin Liu [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=ZLDA4dT+pF6AeTP3@Laptop-X1 \
    --to=liuhangbin@gmail.com \
    --cc=aclaudi@redhat.com \
    --cc=dsahern@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=yinxu@redhat.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).