From: Mingming <cmm@us.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Gary Hawco <ghawco@cox.net>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Problem compiling 2.6.260rc6 with updated ext4-patch-queue
Date: Tue, 24 Jun 2008 15:34:45 -0700 [thread overview]
Message-ID: <1214346885.27507.327.camel@BVR-FS.beaverton.ibm.com> (raw)
In-Reply-To: <20080624221845.GK7639@mit.edu>
On Tue, 2008-06-24 at 18:18 -0400, Theodore Tso wrote:
> On Tue, Jun 24, 2008 at 10:26:59AM +0000, Gary Hawco wrote:
> > Recently pulled and updated my ext4-patch-queue. Tried to compile
> > the 2.6.26-rc6 after it patched cleanly. During make received the
> > following error.
>
> Hmm.... I just tested the latest commit on the ext4 patch queue
> (14581cb30), and it compiled just fine on 2.6.26-rc6.
Sorry! My bad. I accidently remove wrong patch when folding the bug
fixes to the parent patch. I did bring that patch back now Gary has
confirmed it compiles fine.
Mingming
prev parent reply other threads:[~2008-06-24 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 10:26 Problem compiling 2.6.260rc6 with updated ext4-patch-queue Gary Hawco
2008-06-24 22:18 ` Theodore Tso
2008-06-24 22:34 ` Mingming [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=1214346885.27507.327.camel@BVR-FS.beaverton.ibm.com \
--to=cmm@us.ibm.com \
--cc=ghawco@cox.net \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox