From: Wolfgang Grandegger <wg@grandegger.com>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: net tree build warning
Date: Tue, 09 Jun 2009 15:14:38 +0200 [thread overview]
Message-ID: <4A2E603E.3040603@grandegger.com> (raw)
In-Reply-To: <20090609.042625.194310688.davem@davemloft.net>
David Miller wrote:
> From: Wolfgang Grandegger <wg@grandegger.com>
> Date: Tue, 09 Jun 2009 13:25:27 +0200
>
>> [PATCH] can: sja1000_of_platform: fix build problems with printk format
>>
>> Variables of type size_t should be printed with the format "%zx".
>>
>> Signed-off-by: Wolfgang Grandegger <wg@grandegger.com>
>
> It's not a "size_t", it's a "resource_size_t" which can be
> "unsigned long long" on some platforms.
Right, but I assume that the %zx handles that type properly as well.
Should I send a patch with a corrected patch description?
Wolfgang.
next prev parent reply other threads:[~2009-06-09 13:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 10:36 linux-next: net tree build warning Stephen Rothwell
2009-06-09 11:25 ` Wolfgang Grandegger
2009-06-09 11:26 ` David Miller
2009-06-09 13:14 ` Wolfgang Grandegger [this message]
2009-06-10 0:38 ` David Miller
2009-06-10 7:38 ` Wolfgang Grandegger
2009-06-10 8:12 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2009-11-30 5:40 Stephen Rothwell
2009-11-30 9:49 ` Andrei Pelinescu-Onciul
2009-11-12 2:24 Stephen Rothwell
2009-11-12 2:53 ` David Miller
2009-11-12 2:55 ` Eric Dumazet
2009-11-12 3:10 ` Stephen Rothwell
2009-11-05 2:30 Stephen Rothwell
[not found] <20090904144232.1f6ccf45.sfr@canb.auug.org.au>
2009-09-07 9:04 ` David Miller
2009-09-07 9:37 ` Stephen Rothwell
2009-09-04 4:28 Stephen Rothwell
2009-09-04 4:35 ` David Miller
2009-05-22 5:16 Stephen Rothwell
2009-05-22 6:30 ` David Miller
2009-05-22 8:20 ` Stephen Rothwell
2009-05-22 10:31 ` Neil Horman
2009-03-12 5:58 Stephen Rothwell
2009-03-12 6:24 ` David Miller
2009-03-12 6:42 ` Stephen Rothwell
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=4A2E603E.3040603@grandegger.com \
--to=wg@grandegger.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 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.