From: Artem Bityutskiy <dedekind1@gmail.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cfi.h: quiet sparse noise
Date: Tue, 02 Feb 2010 07:58:25 +0200 [thread overview]
Message-ID: <1265090305.2517.13.camel@localhost.localdomain> (raw)
In-Reply-To: <201001151109.32890.hartleys@visionengravers.com>
On Fri, 2010-01-15 at 11:09 -0700, H Hartley Sweeten wrote:
> cfi.h: quiet sparse noise
>
> In the inline function cfi_build_cmd_addr, the cast of cmd_ofs to an
> uint8_t produces a sparse warning of the type:
>
> warning: cast truncates bits from constant value (2aa becomes aa)
>
> Quiet the warning by masking cmd_ofs with 0xff and remove the cast.
>
> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> Cc: David Woodhouse <dwmw2@infradead.org>
Pushed this one to my l2-mtd-2.6 / master
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-02-02 5:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 18:09 [PATCH] cfi.h: quiet sparse noise H Hartley Sweeten
2010-02-02 5:58 ` Artem Bityutskiy [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=1265090305.2517.13.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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