From: Al Viro <viro@ZenIV.linux.org.uk>
To: Sathya Perla <Sathya.Perla@Emulex.Com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: sparse warning about endianness mismatch on 0xffff assignment
Date: Thu, 16 Apr 2015 21:57:39 +0100 [thread overview]
Message-ID: <20150416205739.GY889@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CF9D1877D81D214CB0CA0669EFAE020C74CF869F@CMEXMB1.ad.emulex.com>
On Thu, Apr 16, 2015 at 06:04:40AM +0000, Sathya Perla wrote:
> What would be the best way of fixing this warning?
>
> a) __le16 var = cpu_to_le16(0xFFFF);
That would do just fine - it's a constant expression, actually.
prev parent reply other threads:[~2015-04-16 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 6:04 sparse warning about endianness mismatch on 0xffff assignment Sathya Perla
2015-04-16 20:57 ` Al Viro [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=20150416205739.GY889@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=Sathya.Perla@Emulex.Com \
--cc=linux-kernel@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.