From: David Miller <davem@davemloft.net>
To: mike.rapoport@ravellosystems.com
Cc: netdev@vger.kernel.org, stephen@networkplumber.org
Subject: Re: [PATCH net-next] vxlan: use htonl when snooping for loopback address
Date: Sun, 14 Apr 2013 15:43:48 -0400 (EDT) [thread overview]
Message-ID: <20130414.154348.2275229894750194737.davem@davemloft.net> (raw)
In-Reply-To: <1365931299-26240-1-git-send-email-mike.rapoport@ravellosystems.com>
From: Mike Rapoport <mike.rapoport@ravellosystems.com>
Date: Sun, 14 Apr 2013 12:21:39 +0300
> Currently "bridge fdb show dev vxlan0" lists loopback address as
> "1.0.0.127". Using htonl(INADDR_LOOPBACK) rather than passing it
> directly to vxlan_snoop fixes the problem.
>
> Signed-off-by: Mike Rapoport <mike.rapoport@ravellosystems.com>
Applied.
prev parent reply other threads:[~2013-04-14 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 9:21 [PATCH net-next] vxlan: use htonl when snooping for loopback address Mike Rapoport
2013-04-14 15:07 ` Cong Wang
2013-04-14 16:57 ` Stephen Hemminger
2013-04-14 19:43 ` 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=20130414.154348.2275229894750194737.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mike.rapoport@ravellosystems.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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).