From: Bob Copeland <me@bobcopeland.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] omfs: sparse annotations
Date: Mon, 28 Jul 2008 21:27:06 -0400 [thread overview]
Message-ID: <20080729012706.GA1775@hash.localnet> (raw)
In-Reply-To: <1217291327.23389.1.camel@brick>
On Mon, Jul 28, 2008 at 05:28:46PM -0700, Harvey Harrison wrote:
> Missing cpu_to_be64 on some constant assignments.
>
> - oi->i_sibling = ~0ULL;
> + oi->i_sibling = ~cpu_to_be64(0ULL);
Thanks, I saw these sparse warnings before but wasn't sure how to fix
them.
Acked-by: Bob Copeland <me@bobcopeland.com>
--
Bob Copeland %% www.bobcopeland.com
prev parent reply other threads:[~2008-07-29 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 0:28 [PATCH] omfs: sparse annotations Harvey Harrison
2008-07-29 1:27 ` Bob Copeland [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=20080729012706.GA1775@hash.localnet \
--to=me@bobcopeland.com \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox