From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Guan Xuetao <gxt@mprc.pku.edu.cn>
Subject: Re: [PATCH] fs/ext4/extents_status.c: fix 64-bit number truncation bug
Date: Mon, 07 Apr 2014 07:58:14 +0800 [thread overview]
Message-ID: <5341EA16.6030705@gmail.com> (raw)
In-Reply-To: <CAMuHMdVT9O8C0fhMbaqS2nB1jfLAZtanp6YGPU6Q-T5b7=n20Q@mail.gmail.com>
On 04/06/2014 09:39 PM, Geert Uytterhoeven wrote:
> On Mon, Mar 31, 2014 at 3:16 PM, Chen Gang <gang.chen.5i5j@gmail.com> 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 <gang.chen.5i5j@gmail.com>
>
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
>
[...]
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-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-04-06 23:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 13:16 [PATCH] fs/ext4/extents_status.c: fix 64-bit number truncation bug Chen Gang
2014-04-04 9:18 ` Chen Gang
2014-04-06 13:39 ` Geert Uytterhoeven
2014-04-06 23:58 ` Chen Gang [this message]
2014-04-07 4:14 ` Theodore Ts'o
2014-04-07 5:00 ` Chen Gang
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=5341EA16.6030705@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=geert@linux-m68k.org \
--cc=gxt@mprc.pku.edu.cn \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).