[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081201114004.731cec86@infradead.org>
Date: Mon, 1 Dec 2008 11:40:04 -0800
From: Arjan van de Ven <arjan@...radead.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Frederik Deweerdt <frederik.deweerdt@...og.eu>, arvidjaar@...l.ru,
linux-kernel@...r.kernel.org, philipl@...rt.org,
linux-acpi@...r.kernel.org
Subject: Re: [patch] ACPI toshiba: only register rfkill if bt is enabled
On Mon, 1 Dec 2008 11:30:52 -0800
Andrew Morton <akpm@...ux-foundation.org> wrote:
> This patch:
>
> On Wed, 29 Oct 2008 08:19:34 +0000
> Frederik Deweerdt <frederik.deweerdt@...og.eu> wrote:
>
> > Register toshiba RFKill Switch only if bluetooth is enabled
>
> which is here:
> http://userweb.kernel.org/~akpm/mmotm/broken-out/acpi-toshiba-only-register-rfkill-if-bt-is-enabled.patch
>
> fixes a post-2.6.27 regression. It doesn't apply any more, due to the
> recent merge of this:
>
> commit e251fa12fb5713e722029341c03b2f48bcd7b7be
> Author: Arjan van de Ven <arjan@...ux.intel.com>
> Date: Fri Nov 28 08:19:09 2008 -0800
>
> toshiba_acpi: close race in toshiba_acpi driver
>
> in linux-next.
>
> It is unclear to me whether these two patches fix the same bug, or
> different ones.
>
they fix the same symptom, but are both needed.
My patch fixes "if it goes wrong and init fails, don't oops", the mmotm
patch fixes "lets not make init fail for <this case>". If there's some
other reason the init fails, my patch is still needed.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
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