Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754666AbaDFX61 (ORCPT ); Sun, 6 Apr 2014 19:58:27 -0400 Received: from mail-pd0-f178.google.com ([209.85.192.178]:47248 "EHLO mail-pd0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754608AbaDFX6X (ORCPT ); Sun, 6 Apr 2014 19:58:23 -0400 Message-ID: <5341EA16.6030705@gmail.com> Date: Mon, 07 Apr 2014 07:58:14 +0800 From: Chen Gang User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Geert Uytterhoeven CC: "Theodore Ts'o" , Andreas Dilger , linux-ext4@vger.kernel.org, "linux-kernel@vger.kernel.org" , Guan Xuetao Subject: Re: [PATCH] fs/ext4/extents_status.c: fix 64-bit number truncation bug References: <53396AC1.10108@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/06/2014 09:39 PM, Geert Uytterhoeven wrote: > On Mon, Mar 31, 2014 at 3:16 PM, Chen Gang wrote: >> '0x7FDEADBEEF' will be truncated to 32-bit number under unicore32. Need >> append 'ULL' for it. >> >> The related warning (with allmodconfig under unicore32): >> >> CC [M] fs/ext4/extents_status.o >> fs/ext4/extents_status.c: In function ‘__es_remove_extent’: >> fs/ext4/extents_status.c:813: warning: integer constant is too large for ‘long’ type > > Thanks! This is failing on all 32-bit architectures. > Yeah. >> Signed-off-by: Chen Gang > > Acked-by: Geert Uytterhoeven > [...] Thank you very much! I will/should continue, and try to finish unicore32 within this month (although, excuse me, in this week and next week, I will have no much free time on open source). Thanks. -- Chen Gang Open, share, and attitude like air, water, and life which God blessed -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/