mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] XFS warning on sparc64
Date: Fri, 7 May 2004 05:58:29 +1000	[thread overview]
Message-ID: <20040507055829.A229613@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <Pine.GSO.4.44.0405061920450.21792-100000@math.ut.ee>; from mroos@linux.ee on Thu, May 06, 2004 at 08:33:06PM +0300

On Thu, May 06, 2004 at 08:33:06PM +0300, Meelis Roos wrote:
> This is 2.6.6-rc3+BK as of today on a sparc64 (gcc 3.3.3 on Debian):
> 
>   CC [M]  fs/xfs/xfs_buf_item.o
> fs/xfs/xfs_buf_item.c: In function `xfs_buf_iodone_callbacks':
> fs/xfs/xfs_buf_item.c:1055: warning: long long unsigned int format, xfs_daddr_t arg (arg 3)
> 
> The following patch seems to fix it - is it correct?
> 
> ===== fs/xfs/xfs_buf_item.c 1.16 vs edited =====
> --- 1.16/fs/xfs/xfs_buf_item.c	Mon Feb  9 06:12:20 2004
> +++ edited/fs/xfs/xfs_buf_item.c	Thu May  6 20:09:01 2004
> @@ -1053,7 +1053,7 @@
>  		    (time_after(jiffies, (lasttime + 5*HZ)))) {
>  			lasttime = jiffies;
>  			prdev("XFS write error in file system meta-data "
> -			      "block 0x%Lx in %s",
> +			      "block 0x%Zx in %s",
>  			      XFS_BUF_TARGET(bp),
>  			      XFS_BUF_ADDR(bp), mp->m_fsname);
>  		}

In most other places we've used %llu and an explicit cast to 
(unsigned long long) when dumping block numbers - I'll fix
that one up.

thanks.

-- 
Nathan

      reply	other threads:[~2004-05-06 19:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06 17:33 Meelis Roos
2004-05-06 19:58 ` Nathan Scott [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=20040507055829.A229613@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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

all inboxes | Powered by JetHome®