public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Fasheh <mfasheh@suse•com>
To: Randy Dunlap <randy.dunlap@oracle•com>
Cc: linux-fsdevel@vger•kernel.org, akpm <akpm@linux-foundation•org>,
	linux-next@vger•kernel.org, ocfs2-devel@oss•oracle.com
Subject: Re: [PATCH -next] ocfs2: fix printk format warnings with OCFS2_FS_STATS=n
Date: Wed, 28 May 2008 14:48:57 -0700	[thread overview]
Message-ID: <20080528214857.GG8325@wotan.suse.de> (raw)
In-Reply-To: <20080528144100.13ec8c6a.randy.dunlap@oracle.com>

On Wed, May 28, 2008 at 02:41:00PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle•com>
> 
> Fix printk format warnings when OCFS2_FS_STATS=n:
> 
> linux-next-20080528/fs/ocfs2/dlmglue.c: In function 'ocfs2_dlm_seq_show':
> linux-next-20080528/fs/ocfs2/dlmglue.c:2623: warning: format '%llu' expects type 'long long unsigned int', but argument 3 has type 'int'
> linux-next-20080528/fs/ocfs2/dlmglue.c:2623: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'int'
> linux-next-20080528/fs/ocfs2/dlmglue.c:2623: warning: format '%llu' expects type 'long long unsigned int', but argument 7 has type 'int'
> linux-next-20080528/fs/ocfs2/dlmglue.c:2623: warning: format '%llu' expects type 'long long unsigned int', but argument 8 has type 'int'
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle•com>

Thanks Randy...
	--Mark

--
Mark Fasheh

      reply	other threads:[~2008-05-28 21:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 21:41 [PATCH -next] ocfs2: fix printk format warnings with OCFS2_FS_STATS=n Randy Dunlap
2008-05-28 21:48 ` Mark Fasheh [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=20080528214857.GG8325@wotan.suse.de \
    --to=mfasheh@suse$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=linux-fsdevel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=ocfs2-devel@oss$(echo .)oracle.com \
    --cc=randy.dunlap@oracle$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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