From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Theodore Tso <tytso@mit.edu>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Kernel BUG] ext4 for v2.6.32 round II
Date: Thu, 1 Oct 2009 05:47:16 +0200 [thread overview]
Message-ID: <20091001034716.GA2008@phenom2.trippelsdorf.de> (raw)
In-Reply-To: <20091001030151.GR24383@mit.edu>
On Wed, Sep 30, 2009 at 11:01:51PM -0400, Theodore Tso wrote:
> Hi Markus,
>
> I'm pretty sure the following should fix your problems; can you
> confirm?
Yes, everything is fine again.
Thank you.
--
Markus
next prev parent reply other threads:[~2009-10-01 3:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 5:25 [GIT PULL] ext4 for v2.6.32 round II Theodore Ts'o
2009-10-01 1:41 ` [Kernel BUG] " Markus Trippelsdorf
2009-10-01 1:57 ` Linus Torvalds
2009-10-01 2:15 ` Markus Trippelsdorf
2009-10-01 3:01 ` Theodore Tso
2009-10-01 3:47 ` Markus Trippelsdorf [this message]
2009-10-01 6:40 ` Theodore Tso
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=20091001034716.GA2008@phenom2.trippelsdorf.de \
--to=markus@trippelsdorf.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).