From: Theodore Tso <tytso@mit.edu>
To: Julia Lawall <julia@diku.dk>
Cc: sandeen@redhat.com, cmm@us.ibm.com,
Andreas Dilger <adilger@sun.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] fs/ext4: test the i_flags field of the right structure
Date: Sat, 14 Nov 2009 20:53:52 -0500 [thread overview]
Message-ID: <20091115015352.GA4323@mit.edu> (raw)
In-Reply-To: <Pine.LNX.4.64.0911022158190.4930@ask.diku.dk>
On Mon, Nov 02, 2009 at 09:58:47PM +0100, Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> Elsewhere, EXT4_EXTENTS_FL is combined with EXT4_I(inode)->i_flags, rather
> than inode->i_flags.
>
> Signed-off-by: Julia Lawall <julia@diku.dk>
Applied to the ext4 patch queue, thanks.
- Ted
prev parent reply other threads:[~2009-11-15 1:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 20:58 [PATCH] fs/ext4: test the i_flags field of the right structure Julia Lawall
2009-11-02 21:22 ` Eric Sandeen
2009-11-15 1:53 ` Theodore Tso [this message]
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=20091115015352.GA4323@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=cmm@us.ibm.com \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
/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