From: roopa <roopa@cumulusnetworks.com>
To: Andrew Vagin <avagin@openvz.org>
Cc: Stephen Hemminger <shemminger@osdl.org>,
netdev@vger.kernel.org, Vadim Kochan <vadim4j@gmail.com>,
Sven-Haegar Koch <haegar@sdinet.de>
Subject: Re: [PATCH] lib utils: use a correct variable to get address length
Date: Mon, 23 Mar 2015 14:53:22 -0700 [thread overview]
Message-ID: <55108B52.8050904@cumulusnetworks.com> (raw)
In-Reply-To: <1427145369-29477-1-git-send-email-avagin@openvz.org>
On 3/23/15, 2:16 PM, Andrew Vagin wrote:
> dst->famaly is initialized in get_addr_1()
>
> This patch fixes errors like this:
> $ ip r a 10.31.0.0/16 dev br0
> Error: an inet prefix is expected rather than "10.31.0.0/16".
>
> Cc: Vadim Kochan <vadim4j@gmail.com>
> Fixes: f3a2ddc124e0 ("lib utils: Use helpers to get AF bit/byte len")
> Signed-off-by: Andrew Vagin <avagin@openvz.org>
I have already submitted similar patch
https://patchwork.ozlabs.org/patch/451210/
prev parent reply other threads:[~2015-03-23 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 21:16 [PATCH] lib utils: use a correct variable to get address length Andrew Vagin
2015-03-23 21:53 ` roopa [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=55108B52.8050904@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=avagin@openvz.org \
--cc=haegar@sdinet.de \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=vadim4j@gmail.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