From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: saurabh.mohan@vyatta.com, netdev@vger.kernel.org
Subject: Re: [PATCH] vti: fix sparse bit endian warnings
Date: Fri, 12 Oct 2012 13:57:31 -0400 (EDT) [thread overview]
Message-ID: <20121012.135731.1351722594734413056.davem@davemloft.net> (raw)
In-Reply-To: <20121011155128.64774827@nehalam.linuxnetplumber.net>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Thu, 11 Oct 2012 15:51:28 -0700
> Use be32_to_cpu instead of htonl to keep sparse happy.
>
> Signed-off-by: Stephen Hemminger <shemminger@vyatta.org>
Using ntohl() would have been just as appropriate a fix, but
whatever, applied. Thanks.
prev parent reply other threads:[~2012-10-12 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 22:51 [PATCH] vti: fix sparse bit endian warnings Stephen Hemminger
2012-10-12 17:57 ` 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=20121012.135731.1351722594734413056.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=saurabh.mohan@vyatta.com \
--cc=shemminger@vyatta.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).