The patch titled
     fix getblk_slow "integer constant is too large" warning
has been added to the -mm tree.  Its filename is
     getblk-handle-2tb-devices-fix.patch

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this

------------------------------------------------------
Subject: fix getblk_slow "integer constant is too large" warning
From: Frederik Deweerdt <[EMAIL PROTECTED]>

On Tue, Nov 06, 2007 at 02:33:53AM -0800, [EMAIL PROTECTED] wrote:
> The mm snapshot broken-out-2007-11-06-02-32.tar.gz has been uploaded to
>
>    
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-11-06-02-32.tar.gz
>
> It contains the following patches against 2.6.24-rc1:
>
[...]
> getblk-handle-2tb-devices.patch
[...]
0xffffffff00000000 is unsigned long long on 32 bits
fs/buffer.c: In function '__getblk_slow':
fs/buffer.c:1126: warning: integer constant is too large for 'unsigned long' 
type

Signed-off-by: Frederik Deweerdt <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 fs/buffer.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff -puN fs/buffer.c~getblk-handle-2tb-devices-fix fs/buffer.c
--- a/fs/buffer.c~getblk-handle-2tb-devices-fix
+++ a/fs/buffer.c
@@ -1123,7 +1123,7 @@ __getblk_slow(struct block_device *bdev,
 
 #if (BITS_PER_LONG == 32) && defined(CONFIG_LBD)
        if ((block >> (PAGE_CACHE_SHIFT - bdev->bd_inode->i_blkbits)) &
-                       0xffffffff00000000UL) {
+                       0xffffffff00000000ULL) {
                /*
                 * We'll fail because the block is outside the range
                 * which a 32-bit pagecache index can address
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

revoke-core-code.patch
reiser4-sb_sync_inodes.patch
getblk-handle-2tb-devices-fix.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to