[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080623193650.GB20535@elte.hu>
Date: Mon, 23 Jun 2008 21:36:50 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Greg KH <greg@...ah.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Theodore Ts'o <tytso@....edu>,
Zwane Mwaikambo <zwane@....linux.org.uk>,
Bernhard Walle <bwalle@...e.de>, Greg KH <gregkh@...e.de>,
Justin Forbes <jmforbes@...uxtx.org>,
Johannes Weiner <hannes@...urebad.de>,
Chris Wedgwood <reviews@...cw.f00f.org>,
linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...otime.net>,
Willy Tarreau <w@....eu>, Michael Krufky <mkrufky@...uxtv.org>,
alan@...rguk.ukuu.org.uk, Chuck Ebbert <cebbert@...hat.com>,
Domenico Andreoli <cavokz@...il.com>,
Dave Jones <davej@...hat.com>, akpm@...ux-foundation.org,
Chuck Wolber <chuckw@...ntumlinux.com>, stable@...nel.org,
Rodrigo Rubira Branco <rbranco@...checkpoint.com>
Subject: Re: [stable] [patch 4/5] x86: use BOOTMEM_EXCLUSIVE on 32-bit
* Greg KH <greg@...ah.com> wrote:
> > thanks. This patch (which was not a build fix but an infrastructure
> > fix that the kexec fix in arch/x86 depended on) is well-tested as
> > well, it was queued in -tip on June 10th:
> >
> > | commit 91d48fc80f22817332170082e10de60a75851640
> > | Author: Bernhard Walle <bwalle@...e.de>
> > | Date: Sun Jun 8 15:46:29 2008 +0200
> > | CommitDate: Tue Jun 10 14:41:56 2008 +0200
> > |
> > | bootmem: add return value to reserve_bootmem_node()
> > |
> > | This patch changes the function reserve_bootmem_node() from void to
> > | int, returning -ENOMEM if the allocation fails.
> > |
> > | Signed-off-by: Bernhard Walle <bwalle@...e.de>
> > | Signed-off-by: Ingo Molnar <mingo@...e.hu>
> >
> > so it is a -stable candidate just as much as the kexec fix. (These
> > are all fixes for long-standing problems so i guess it can go all
> > the way back to all stable kernels that are being maintained.)
>
> Hm, but it's not in Linus's tree yet, so I can't take it for stable at
> this time :(
it's all fine already: it's the very same patch you just added, but
different sha1. I just pointed out the lineage and the testing status of
the patch.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists