From: "Theodore Ts'o" <tytso@mit.edu>
To: Jiri Slaby <jslaby@suse.cz>
Cc: boyu.mt@taobao.com, linux-ext4@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: next: ext4 build failure
Date: Tue, 4 Dec 2012 08:27:01 -0500 [thread overview]
Message-ID: <20121204132701.GA29083@thunk.org> (raw)
In-Reply-To: <50BDC25C.5020509@suse.cz>
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!!!
- Ted
next prev parent reply other threads:[~2012-12-04 13:27 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 [this message]
2012-12-04 13:29 ` Jiri Slaby
2012-12-04 13:40 ` Tao Ma
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=20121204132701.GA29083@thunk.org \
--to=tytso@mit.edu \
--cc=boyu.mt@taobao.com \
--cc=jslaby@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).