From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Guenter Roeck <guenter@roeck-us.net>
Cc: Wim Van Sebroeck <wim@iguana.be>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Aaron Sierra <asierra@xes-inc.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Randy Dunlap <rdunlap@xenotime.net>,
linux-watchdog@vger.kernel.org, Jean Delvare <khali@linux-fr.org>
Subject: Re: linux-next: manual merge of the watchdog tree with the mfd tree
Date: Wed, 23 May 2012 08:46:39 +1000 [thread overview]
Message-ID: <20120523084639.bbc57455a6527c9cb983fb2d@canb.auug.org.au> (raw)
In-Reply-To: <6.2.5.6.2.20120522153050.0284ee38@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
Hi guys,
On Tue, 22 May 2012 15:37:04 -0700 Guenter Roeck <guenter@roeck-us.net> wrote:
>
> >I don't think we have a clear standard yet, but I'm fine with either
> >one of them.
>
> Me too, though %04lx and typecast to long should really be sufficient.
>
> I'd guess the change was made because resource_size_t is sometimes a long
> and sometimes a long long, depending on the platform. I hit that
> problem a couple of times myself.
Exactly. Since resource_size_t can be either 32 bit or 64 bit on 32 bit
platforms, you must print it as %llx and cast it to u64 always to
prevent these warnings. If you cast it to (unsigned) long you could
possibly truncate the value.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-22 22:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 5:23 linux-next: manual merge of the watchdog tree with the mfd tree Stephen Rothwell
2012-05-18 8:32 ` Wim Van Sebroeck
2012-05-19 1:20 ` Guenter Roeck
2012-05-22 16:35 ` Wim Van Sebroeck
2012-05-22 22:37 ` Guenter Roeck
2012-05-22 22:46 ` Stephen Rothwell [this message]
2012-05-23 5:44 ` Wim Van Sebroeck
2012-05-23 14:26 ` Samuel Ortiz
2012-05-23 14:55 ` Wim Van Sebroeck
2013-02-08 1:52 Stephen Rothwell
2013-02-08 11:36 ` Wim Van Sebroeck
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=20120523084639.bbc57455a6527c9cb983fb2d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=asierra@xes-inc.com \
--cc=guenter@roeck-us.net \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sameo@linux.intel.com \
--cc=wim@iguana.be \
/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.