From: "Randy.Dunlap" <rddunlap@osdl.org>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] procfs: fix printk format warning
Date: Thu, 03 Mar 2005 02:49:05 +0000 [thread overview]
Message-ID: <42267B21.2020405@osdl.org> (raw)
In-Reply-To: <20050301211005.6a23f2b4.rddunlap@osdl.org>
William Lee Irwin III wrote:
> On Tue, Mar 01, 2005 at 09:10:05PM -0800, Randy.Dunlap wrote:
>
>>sparc: fix printk format warning:
>>fs/proc/proc_misc.c:195: warning: long unsigned int format, unsigned int arg (arg 23)
>>Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
>>diffstat:>> include/asm-sparc/vaddrs.h | 4 ++--
>> 1 files changed, 2 insertions(+), 2 deletions(-)
>
>
> The UL qualifier can't be used directly as VMALLOC_START is used in
> assembly (check arch/sparc/kernel/entry.S).
Darn, that gives me some lack of confidence in my cross-build
tools. Cross-build results are at:
https://www.osdl.org/plm-cgi/plm?module=patch_info&patch_idB38
and sparc build with this patch passed....
But I do trust that you know what you are talking about and
that I probably have a toolchain problem.
--
~Randy
next prev parent reply other threads:[~2005-03-03 2:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 5:10 [PATCH] procfs: fix printk format warning Randy.Dunlap
2005-03-03 2:03 ` William Lee Irwin III
2005-03-03 2:49 ` Randy.Dunlap [this message]
2005-03-03 11:02 ` William Lee Irwin III
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=42267B21.2020405@osdl.org \
--to=rddunlap@osdl.org \
--cc=sparclinux@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.