From: William Lee Irwin III <wli@holomorphy.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] silence numerous size_t warnings in drivers/acpi/processor_idle.c
Date: Tue, 11 Jan 2005 12:36:29 -0800 [thread overview]
Message-ID: <20050111203629.GB14443@holomorphy.com> (raw)
In-Reply-To: <41E436AC.1050004@osdl.org>
ChangeSet 1.2334, 2005/01/11 09:21:40-08:00, wli@holomorphy.com
>> [PATCH] silence numerous size_t warnings in
>> drivers/acpi/processor_idle.c
>> Multiple format -related warnings arise from size_t issues. This
>> patch
>> peppers the seq_printf()'s with 'z' qualifiers and casts to silence
>> them all.
On Tue, Jan 11, 2005 at 12:27:24PM -0800, Randy.Dunlap wrote:
> Does this mean that ptrdiff_t type looks same as a size_t
> to printk() & seq_printf() ?
As far as I know this is the case. I have no specific opinion on this
being a better way to do it than something else.
-- wli
prev parent reply other threads:[~2005-01-11 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200501111916.j0BJGq1F010042@hera.kernel.org>
2005-01-11 20:27 ` [PATCH] silence numerous size_t warnings in drivers/acpi/processor_idle.c Randy.Dunlap
2005-01-11 20:36 ` William Lee Irwin III [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=20050111203629.GB14443@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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;
as well as URLs for NNTP newsgroup(s).