All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 01/14] ocfs2: fix -Wformat warnings when building UML on x86-64
Date: Tue, 21 Feb 2006 19:37:41 +0100	[thread overview]
Message-ID: <20060221183740.GA3068@lst.de> (raw)
In-Reply-To: <20060221165730.GA11821@locomotive.unixthugs.org>

On Tue, Feb 21, 2006 at 11:57:30AM -0500, Jeff Mahoney wrote:
> 
>  The check to determine which format string is appopriate for u64 and
>  friends works in most cases, but UML on x86_64 doesn't define CONFIG_X86_64,
>  so it results in screen fulls of compile-time warnings.
> 
>  This patch fixes it to handle that case.
> 
>  fs/ocfs2/cluster/masklog.h |    2 +-
>  1 files changed, 1 insertion(+), 1 deletion(-)
> 
> Signed-off-by: Jeff Mahoney <jeffm@suse.com>
> 
> diff -ruNpX ../dontdiff linux-2.6.16-rc4.ocfs2-staging1/fs/ocfs2/cluster/masklog.h linux-2.6.16-rc4.ocfs2-staging2/fs/ocfs2/cluster/masklog.h
> --- linux-2.6.16-rc4.ocfs2-staging1/fs/ocfs2/cluster/masklog.h	2006-02-21 11:41:25.000000000 -0500
> +++ linux-2.6.16-rc4.ocfs2-staging2/fs/ocfs2/cluster/masklog.h	2006-02-21 11:44:25.000000000 -0500
> @@ -255,7 +255,7 @@ extern struct mlog_bits mlog_and_bits, m
>  	}								\
>  } while (0)
>  
> -#if (BITS_PER_LONG == 32) || defined(CONFIG_X86_64)
> +#if (BITS_PER_LONG == 32) || defined(CONFIG_X86_64) || (defined(CONFIG_UML_X86) && defined(CONFIG_64BIT))
>  #define MLFi64 "lld"
>  #define MLFu64 "llu"
>  #define MLFx64 "llx"

Please just rip out this crap instead and use the normal
(long long) or (unsigned long long) casts used everywhere else in the
kernel.

  reply	other threads:[~2006-02-21 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 16:57 [Ocfs2-devel] [PATCH 01/14] ocfs2: fix -Wformat warnings when building UML on x86-64 Jeff Mahoney
2006-02-21 18:37 ` Christoph Hellwig [this message]
2006-02-21 21:41   ` Mark Fasheh

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=20060221183740.GA3068@lst.de \
    --to=hch@lst.de \
    --cc=ocfs2-devel@oss.oracle.com \
    /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.