From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Michael Schmitz <schmitz@zirkon.biophys.uni-duesseldorf.de>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Adrian Bunk <bunk@kernel.org>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-m68k@vger.kernel.org
Subject: Re: 2.6.25-rc8-mm2
Date: Sun, 13 Apr 2008 10:11:46 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0804131010090.28304@anakin> (raw)
In-Reply-To: <alpine.DEB.1.00.0804130944380.1190@zirkon.biophys.uni-duesseldorf.de>
On Sun, 13 Apr 2008, Michael Schmitz wrote:
> > > I saw some related linux-ext4 email float past yesterday, so something
> > > might be happening.
> >
> > It would really help if we can get some m68k people to look at patch
> > i posted.
> >
> > http://article.gmane.org/gmane.comp.file-systems.ext4/5944
>
> I'd love to - only I can't seem to compile 2.6.25 at all. What's the minimum
> gcc version I should use?
My cross-compiler is gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21).
Gr{oetje,eeting}s,
Geert
P.S. I'll look into it when I find some time, but you may beat me to it...
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2008-04-13 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080410203354.f0a6f464.akpm@linux-foundation.org>
[not found] ` <20080411134036.GB3821@cs181133002.pp.htv.fi>
2008-04-12 4:22 ` 2.6.25-rc8-mm2 Andrew Morton
2008-04-12 18:43 ` 2.6.25-rc8-mm2 Aneesh Kumar K.V
2008-04-13 7:45 ` 2.6.25-rc8-mm2 Michael Schmitz
2008-04-13 8:11 ` Geert Uytterhoeven [this message]
2008-04-14 8:07 ` BUG at __dentry_open [Was: 2.6.25-rc8-mm2] Jiri Slaby
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=Pine.LNX.4.64.0804131010090.28304@anakin \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bunk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitz@zirkon.biophys.uni-duesseldorf.de \
/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