From: Chris Ball <cjb@laptop.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH -next] mmc quirks: fix truncation warnings
Date: Tue, 12 Apr 2011 13:03:23 -0400 [thread overview]
Message-ID: <m339ln1jxg.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <20110412091735.f41a3d44.randy.dunlap@oracle.com> (Randy Dunlap's message of "Tue, 12 Apr 2011 09:17:35 -0700")
Hi,
On Tue, Apr 12 2011, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Fix data truncation warnings: .manfid is not unsigned long:
>
> drivers/mmc/core/quirks.c:36: warning: large integer implicitly truncated to unsigned type
> drivers/mmc/core/quirks.c:40: warning: large integer implicitly truncated to unsigned type
> drivers/mmc/core/quirks.c:43: warning: large integer implicitly truncated to unsigned type
> drivers/mmc/core/quirks.c:46: warning: large integer implicitly truncated to unsigned type
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: Chris Ball <cjb@laptop.org>
> Cc: linux-mmc@vger.kernel.org
> ---
> include/linux/mmc/card.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20110412.orig/include/linux/mmc/card.h
> +++ linux-next-20110412/include/linux/mmc/card.h
> @@ -180,7 +180,7 @@ struct mmc_fixup {
> int data;
> };
>
> -#define CID_MANFID_ANY (-1ul)
> +#define CID_MANFID_ANY (-1u)
> #define CID_OEMID_ANY ((unsigned short) -1)
> #define CID_NAME_ANY (NULL)
>
>
Thanks very much, Randy, I've pushed this to mmc-next.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2011-04-12 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 5:14 linux-next: Tree for April 12 Stephen Rothwell
2011-04-12 16:17 ` [PATCH -next] mmc quirks: fix truncation warnings Randy Dunlap
2011-04-12 17:03 ` Chris Ball [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=m339ln1jxg.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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