From: Jiri Benc <jbenc@redhat.com>
To: Lance Richardson <lrichard@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net] vxlan: fix byte order of vxlan-gpe port number
Date: Tue, 17 Jan 2017 11:15:59 +0100 [thread overview]
Message-ID: <20170117111559.52d9edff@griffin> (raw)
In-Reply-To: <1484609878-7288-1-git-send-email-lrichard@redhat.com>
On Mon, 16 Jan 2017 18:37:58 -0500, Lance Richardson wrote:
> vxlan->cfg.dst_port is in network byte order, so an htons()
> is needed here. Also reduced comment length to stay closer
> to 80 column width (still slightly over, however).
Ouch. A stupid mistake I made. I think it's still okay to fix this, I'm
not aware of anyone using VXLAN-GPE yet, it's main user is going to be
NSH which is still under development.
Acked-by: Jiri Benc <jbenc@redhat.com>
Please apply also to stable.
Thanks,
Jiri
next prev parent reply other threads:[~2017-01-17 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 23:37 [PATCH net] vxlan: fix byte order of vxlan-gpe port number Lance Richardson
2017-01-17 10:15 ` Jiri Benc [this message]
2017-01-17 20:24 ` David Miller
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=20170117111559.52d9edff@griffin \
--to=jbenc@redhat.com \
--cc=lrichard@redhat.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.