From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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 00:13:17 +0530 [thread overview]
Message-ID: <20080412184317.GB18122@skywalker> (raw)
In-Reply-To: <20080411212222.b3c1177e.akpm@linux-foundation.org>
On Fri, Apr 11, 2008 at 09:22:22PM -0700, Andrew Morton wrote:
> On Fri, 11 Apr 2008 16:40:36 +0300 Adrian Bunk <bunk@kernel.org> wrote:
>
> > On Thu, Apr 10, 2008 at 08:33:54PM -0700, Andrew Morton wrote:
> > >...
> > > Changes since 2.6.25-rc8-mm1:
> > >...
> > > +ext4-is-busted-on-m68k.patch
> > >
> > > ext4 doesn't build on m68k
> > >...
> >
> > Is this due to the generic_find_next_le_bit compile error I reported as
> > 2.6.25 regression (there seems to be some discussion recently how to
> > fix it - hopefully for 2.6.25) or is there even more breakage in -mm?
>
> Yes, it's the bitops screwup.
>
> 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
-aneesh
next prev parent reply other threads:[~2008-04-12 18:43 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 ` Aneesh Kumar K.V [this message]
2008-04-13 7:45 ` 2.6.25-rc8-mm2 Michael Schmitz
2008-04-13 8:11 ` 2.6.25-rc8-mm2 Geert Uytterhoeven
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=20080412184317.GB18122@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
/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