public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Alexander Beregalov <a.beregalov@gmail•com>
To: Evgeniy Polyakov <zbr@ioremap•net>
Cc: gregkh@suse•de, linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH next 2/2] pohmelfs: fix printk format warnings
Date: Fri, 13 Feb 2009 17:37:28 +0300	[thread overview]
Message-ID: <a4423d670902130637h8a7addfgd1ddb8fb590dc507@mail.gmail.com> (raw)
In-Reply-To: <20090213131400.GF23879@ioremap.net>

2009/2/13 Evgeniy Polyakov <zbr@ioremap•net>:
> Hi Alexander.
>
> On Fri, Feb 13, 2009 at 03:59:44PM +0300, Alexander Beregalov (a.beregalov@gmail•com) wrote:
>> drivers/staging/pohmelfs/inode.c:917: warning: format '%u' expects type 'unsigned int', but argument 4 has type 'size_t'
>> drivers/staging/pohmelfs/inode.c:1036: warning: format '%u' expects type 'unsigned int', but argument 7 has type 'size_t'
>> drivers/staging/pohmelfs/trans.c:164: warning: format '%u' expects type 'unsigned int', but argument 5 has type '__kernel_size_t'
>> drivers/staging/pohmelfs/trans.c:170: warning: format '%u' expects type 'unsigned int', but argument 7 has type '__kernel_size_t'
>> drivers/staging/pohmelfs/trans.c:517: warning: format '%u' expects type 'unsigned int', but argument 6 has type '__kernel_size_t'
>> drivers/staging/pohmelfs/trans.c:600: warning: format '%u' expects type 'unsigned int', but argument 6 has type '__kernel_size_t'
>> drivers/staging/pohmelfs/trans.c:610: warning: format '%u' expects type 'unsigned int', but argument 7 has type '__kernel_size_t'
>
> Doesn't size_t have %zu format?
Hi

Thanks for the tip, may I rewrite the patch?

next prev parent reply	other threads:[~2009-02-13 14:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 12:59 [PATCH next 2/2] pohmelfs: fix printk format warnings Alexander Beregalov
2009-02-13 13:08 ` Frank Seidel
2009-02-13 13:14 ` Evgeniy Polyakov
2009-02-13 13:29   ` Frank Seidel
2009-02-13 14:37   ` Alexander Beregalov [this message]
2009-02-13 14:42     ` Evgeniy Polyakov

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=a4423d670902130637h8a7addfgd1ddb8fb590dc507@mail.gmail.com \
    --to=a.beregalov@gmail$(echo .)com \
    --cc=gregkh@suse$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=zbr@ioremap$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox