From: Christoph Hellwig <hch@infradead.org>
To: Andrew Clayton <andrew@digital-domain.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: XFS compilation warning in 2.6.9-rc1
Date: Tue, 24 Aug 2004 13:35:04 +0100 [thread overview]
Message-ID: <20040824133504.A28488@infradead.org> (raw)
In-Reply-To: <1093350616.2237.8.camel@alpha.digital-domain.net>; from andrew@digital-domain.net on Tue, Aug 24, 2004 at 01:30:16PM +0100
On Tue, Aug 24, 2004 at 01:30:16PM +0100, Andrew Clayton wrote:
> CC fs/xfs/xfs_bmap.o
> fs/xfs/xfs_bmap.c: In function `xfs_bmap_do_search_extents':
> fs/xfs/xfs_bmap.c:3434: warning: integer constant is too large for
> "long" type
> fs/xfs/xfs_bmap.c:3435: warning: integer constant is too large for
> "long" type
> CC fs/xfs/xfs_bmap_btree.o
--- 1.26/fs/xfs/xfs_bmap.c 2004-08-19 05:36:06 +02:00
+++ edited/fs/xfs/xfs_bmap.c 2004-08-24 14:35:40 +02:00
@@ -3431,15 +3431,16 @@
* uninitialized br_startblock field.
*/
- got.br_startoff = 0xffa5a5a5a5a5a5a5;
- got.br_blockcount = 0xa55a5a5a5a5a5a5a;
+ got.br_startoff = 0xffa5a5a5a5a5a5a5LL;
+ got.br_blockcount = 0xa55a5a5a5a5a5a5aLL;
got.br_state = XFS_EXT_INVALID;
- #if XFS_BIG_BLKNOS
- got.br_startblock = 0xffffa5a5a5a5a5a5;
- #else
- got.br_startblock = 0xffffa5a5;
- #endif
+#if XFS_BIG_BLKNOS
+ got.br_startblock = 0xffffa5a5a5a5a5a5LL;
+#else
+ got.br_startblock = 0xffffa5a5;
+#endif
+
if (lastx != NULLEXTNUM && lastx < nextents)
ep = base + lastx;
else
next prev parent reply other threads:[~2004-08-24 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 12:30 Andrew Clayton
2004-08-24 12:35 ` Christoph Hellwig [this message]
2004-08-24 13:00 ` Andrew Clayton
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=20040824133504.A28488@infradead.org \
--to=hch@infradead.org \
--cc=andrew@digital-domain.net \
--cc=linux-kernel@vger.kernel.org \
/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®