public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: 2.6.25-rc8-mm2
Date: Fri, 11 Apr 2008 21:22:22 -0700	[thread overview]
Message-ID: <20080411212222.b3c1177e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080411134036.GB3821@cs181133002.pp.htv.fi>

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.


  reply	other threads:[~2008-04-12  4:23 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11  3:33 2.6.25-rc8-mm2 Andrew Morton
2008-04-11  6:28 ` 2.6.25-rc8-mm2: boot hang after "ACPI: using IOAPIC for interrupt routing" Alexey Dobriyan
2008-04-11  6:29 ` Alexey Dobriyan
2008-04-11  6:43   ` Pekka Enberg
2008-04-11 10:35   ` Pekka Enberg
2008-04-11 21:07     ` Alexey Dobriyan
2008-04-11 21:25       ` Pekka J Enberg
2008-04-11 23:09         ` Alexey Dobriyan
2008-04-11  9:57 ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 10:23   ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 10:34     ` 2.6.25-rc8-mm2 Pekka Enberg
2008-04-11 10:57       ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 11:17         ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 13:17           ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 14:24             ` 2.6.25-rc8-mm2 Pekka Enberg
2008-04-14  3:13               ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 13:40 ` 2.6.25-rc8-mm2 Adrian Bunk
2008-04-12  4:22   ` Andrew Morton [this message]
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         ` 2.6.25-rc8-mm2 Geert Uytterhoeven
2008-04-11 23:43 ` 2.6.25-rc8-mm2: panic involving mount_block_root and down the road Alexey Dobriyan
2008-04-12  0:59   ` 2.6.25-rc8-mm2: CONFIG_ATA_SFF: " Alexey Dobriyan
2008-04-12  6:52     ` Adrian Bunk
2008-04-12 10:02       ` Jeff Garzik
2008-04-13  0:45         ` Tejun Heo
2008-04-13  0:51         ` [mm patch] select ATA_SFF Adrian Bunk
2008-04-12  5:53 ` 2.6.25-rc8-mm2 Valdis.Kletnieks
2008-04-12  6:07   ` 2.6.25-rc8-mm2 Andrew Morton
2008-04-12  8:52 ` 2.6.25-rc8-mm2 - CONFIG_PROFILE_LIKELY broke again Valdis.Kletnieks
2008-04-12  9:41 ` 2.6.25-rc8-mm2 Valdis.Kletnieks
2008-04-12 10:47 ` 2.6.25-rc8-mm2 - ftraced chews 100% of a CPU Valdis.Kletnieks
2008-04-13 20:44 ` 2.6.25-rc8-mm2: IP: [<ffffffff802868f9>] __kmalloc+0x69/0x110 Alexey Dobriyan
2008-04-13 20:53   ` Andrew Morton
2008-04-14 16:18     ` Pekka Enberg
2008-04-14 18:00     ` Christoph Lameter
2008-04-14  9:51   ` Pekka J Enberg
2008-04-14 16:01   ` Pekka Enberg
2008-04-14 17:53     ` Christoph Lameter
2008-04-14 17:57       ` Christoph Lameter
2008-04-14 18:32       ` Alexey Dobriyan
2008-04-14 19:56         ` 2.6.25-rc8-mm2: FIX kmalloc-2048 (was Re: 2.6.25-rc8-mm2: IP: [<ffffffff802868f9>] __kmalloc+0x69/0x110) Alexey Dobriyan
2008-04-14 20:05           ` Christoph Lameter
2008-04-19 11:17             ` Alexey Dobriyan
2008-04-19 14:45               ` atl1 64-bit => 32-bit DMA borkage (reproducible, bisected) Alexey Dobriyan
2008-04-20  2:54                 ` Jay Cliburn
2008-04-20 11:14                   ` Alexey Dobriyan
2008-04-20 11:06                     ` Jay Cliburn
2008-04-20 12:26                       ` Alexey Dobriyan
2008-04-20 18:37                         ` Jay Cliburn
2008-04-20 20:55                           ` Alexey Dobriyan
2008-04-21 18:42                             ` Chris Snook
2008-04-21 19:56                               ` Alexey Dobriyan
2008-04-22  2:08                             ` Jay Cliburn
2008-04-22 19:02                               ` Alexey Dobriyan
2008-04-26  0:57                               ` Jay Cliburn
2008-04-28  6:42                                 ` Alexey Dobriyan
2008-05-04 21:15                                 ` Alexey Dobriyan
2008-05-05  0:31                                   ` Jay Cliburn
2008-05-05  0:34                                     ` Jay Cliburn
2008-05-06 16:02                                   ` Jay Cliburn
2008-05-09 19:51                                     ` Alexey Dobriyan
2008-05-09 18:56                                       ` Chris Snook
2008-05-09 20:07                                         ` Alexey Dobriyan
2008-05-09 19:38                                           ` Jay Cliburn
2008-05-10 19:31                                             ` [PATCH] " Alexey Dobriyan
2008-05-11  1:58                                               ` Jay Cliburn
2008-04-14  8:07 ` BUG at __dentry_open [Was: 2.6.25-rc8-mm2] Jiri Slaby
2008-04-15 17:00 ` 2.6.25-rc8-mm2: Observed problems: Not a detailed bug report Zan Lynx
2008-04-15 18:42   ` Andrew Morton
2008-04-15 20:12     ` Rafael J. Wysocki

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=20080411212222.b3c1177e.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@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