From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH iproute2-next v3 0/8] ip: Introduce and use
 get_addr_rta()/inet_addr_match_rta()
Date: Thu, 25 Jan 2018 10:34:09 -0700
Message-ID: <1e104885-f882-b4c1-7fef-604f6f6fe9d8@gmail.com>
References: <1516820200-13723-1-git-send-email-serhe.popovych@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
To: Serhey Popovych <serhe.popovych@gmail.com>, netdev@vger.kernel.org
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-pg0-f45.google.com ([74.125.83.45]:45137 "EHLO
        mail-pg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751086AbeAYReM (ORCPT
        <rfc822;netdev@vger.kernel.org>); Thu, 25 Jan 2018 12:34:12 -0500
Received: by mail-pg0-f45.google.com with SMTP id m136so5477039pga.12
        for <netdev@vger.kernel.org>; Thu, 25 Jan 2018 09:34:12 -0800 (PST)
In-Reply-To: <1516820200-13723-1-git-send-email-serhe.popovych@gmail.com>
Content-Language: en-US
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On 1/24/18 11:56 AM, Serhey Popovych wrote:
> Now we enhance get_addr() to return additional information about address
> (e.g. if it unspecified or multicast) we want to have same functionality
> for attributes in netlink message.
> 
> Introduce and use get_addr_rta() that parses given netlink attribute
> into @inet_prefix data structure in the same way similar get_addr()
> parses address from it's string representation.
> 
> Use attribute length to guess address family: force it by giving non
> AF_UNSPEC @family to get_addr_rta() to ensure address is of expected
> family.
> 
> Introduce and use inet_addr_match_rta() to further simplify and unify
> code where get_addr_rta() intended to be used together with
> inet_addr_match().
> 
> This is next step in ipv4 and ipv6 modules unification to prepare for
> merge in the future.
> 


series applied to iproute2-next. Thanks, Serhey.