linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
Cc: Theodore Tso <tytso@mit.edu>,
	linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
	adilger@sun.com, jack@suse.cz, sandeen@redhat.com
Subject: Re: status of the ext3/jbd error handling enhancement patches
Date: Mon, 20 Oct 2008 23:37:26 -0700	[thread overview]
Message-ID: <20081020233726.5682a278.akpm@linux-foundation.org> (raw)
In-Reply-To: <48FD75AF.6080507@hitachi.com>

On Tue, 21 Oct 2008 15:24:47 +0900 Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com> wrote:

> >>One of the above patches (I forget which) breaks the build because it
> >>expects the presence of Al Viro's VFS tree, and that hasn't been merged
> >>yet.  I need to wait and see if that merge will be happening (seems
> >>unlikely) and if not, rework the patch against mainline.
> 
> I see.  Thank you for your work.
> 
> > Strange; I don't recall any of the ext4 variants of the error handling
> > patches requiring Al's VFS tree.  And I thought all of them have been
> > merged into Linus's tree at this point.
> 
> I checked Al's VFS tree and I found commit
> 6ac465f99b29f74ca5a62bc32a8772985d9a071b changes codes near where
> one of my patch changes (in ext3/ext4_quota_on()), but not the same code.

OK.

Don't worry about it - I'll fix things up some time this week.

  reply	other threads:[~2008-10-21  6:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20  4:25 status of the ext3/jbd error handling enhancement patches Hidehiro Kawai
2008-10-20  5:13 ` Andrew Morton
2008-10-20 12:41   ` Theodore Tso
2008-10-21  6:24     ` Hidehiro Kawai
2008-10-21  6:37       ` Andrew Morton [this message]
2008-10-20 17:17 ` Simon Kirby
2008-10-22  4:54   ` Hidehiro Kawai

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=20081020233726.5682a278.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adilger@sun.com \
    --cc=hidehiro.kawai.ez@hitachi.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --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).