From: Tao Ma <tm@tao.ma>
To: Theodore Ts'o <tytso@mit.edu>, Jiri Slaby <jslaby@suse.cz>,
boyu.mt@taobao.com, linux-ext4@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: next: ext4 build failure
Date: Tue, 04 Dec 2012 21:40:16 +0800 [thread overview]
Message-ID: <50BDFD40.1020202@tao.ma> (raw)
In-Reply-To: <20121204132701.GA29083@thunk.org>
Hi Ted,
On 12/04/2012 09:27 PM, Theodore Ts'o wrote:
> On Tue, Dec 04, 2012 at 10:29:00AM +0100, Jiri Slaby wrote:
>> Hi,
>>
>> commit a7b0168d4a9bb78535827ddaf9c055963f5bd7aa
>> Author: Tao Ma <boyu.mt@taobao.com>
>> Date: Sun Dec 2 20:30:52 2012 -0500
>>
>> ext4: let fallocate handle inline data correctly
>>
>> added
>>
>> static int int ext4_convert_inline_data(struct inode *inode)
>>
>> ^^^^^^^
>>
>> when EXT4_FS_XATTR is unset.
>>
>> Care to fix that?
>
> Oops. Thanks for catching this!!!
Please push the patch with the subject "[PATCH] ext4: Fix inline data
build warning found by kernel build testing." and these error should go
away. And also Dan's smatch has found another issue and I have sent out
the patch with subject "[PATCH] ext4: Fix inline data build warning
found by kernel build testing.".
Thanks
Tao
>
> - Ted
> --
> 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/
>
next prev parent reply other threads:[~2012-12-04 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 9:29 next: ext4 build failure Jiri Slaby
2012-12-04 13:12 ` Tao Ma
2012-12-04 13:27 ` Theodore Ts'o
2012-12-04 13:29 ` Jiri Slaby
2012-12-04 13:40 ` Tao Ma [this message]
2012-12-04 13:42 ` Tao Ma
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=50BDFD40.1020202@tao.ma \
--to=tm@tao.ma \
--cc=boyu.mt@taobao.com \
--cc=jslaby@suse.cz \
--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 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.