From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "Greg Kroah-Hartman" <gregkh@suse.de>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Mark Allyn <mark.a.allyn@intel.com>,
Joe Perches <joe@perches.com>,
Ben Hutchings <ben@decadent.org.uk>,
Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCH 3/3] staging/sep: Fix sparse printk format warning
Date: Mon, 29 Nov 2010 22:59:11 +0100 [thread overview]
Message-ID: <201011292259.12527.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20101129134943.4ef92448.randy.dunlap@oracle.com>
> Are you sure? I'm used to these being gcc warnings, not sparse.
You're right - these are generated by gcc ;) sorry for the confusion.
> Also, this fixes the warnings on x86_64 but not on x86_32/i386:
You're right again, I'm on x86_64 - so what should I use instead?
(atleast the patch fixes the size_t format strings ;)
Peter
next prev parent reply other threads:[~2010-11-29 21:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 21:31 [PATCH 1/3] staging/sep: Fix sparse warning 'do-while statement is not a compound statement' Peter Huewe
2010-11-29 21:31 ` [PATCH 2/3] staging/sep: Fix sparse warning 'Using plain integer as NULL pointer' Peter Huewe
2010-11-29 21:31 ` [PATCH 3/3] staging/sep: Fix sparse printk format warning Peter Huewe
2010-11-29 21:49 ` Randy Dunlap
2010-11-29 21:59 ` Peter Hüwe [this message]
2010-11-29 22:01 ` Randy Dunlap
2010-11-29 23:18 ` Jiri Slaby
2010-12-01 22:52 ` [PATCH 1/3] staging: sep: Fix sparse warning 'do-while statement is not a compound statement' Greg KH
2010-12-01 23:43 ` [PATCH 1/3] staging/sep: " Peter Huewe
2010-12-01 23:43 ` [PATCH 2/3] staging/sep: Fix sparse warning 'Using plain integer as NULL pointer' Peter Huewe
2010-12-01 23:43 ` [PATCH 3/3] staging/sep: Fix printk format warning Peter Huewe
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=201011292259.12527.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=alan@linux.intel.com \
--cc=ben@decadent.org.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.a.allyn@intel.com \
--cc=randy.dunlap@oracle.com \
/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