Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752364AbYLATjM (ORCPT ); Mon, 1 Dec 2008 14:39:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752821AbYLATi5 (ORCPT ); Mon, 1 Dec 2008 14:38:57 -0500 Received: from casper.infradead.org ([85.118.1.10]:59295 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752251AbYLATi4 (ORCPT ); Mon, 1 Dec 2008 14:38:56 -0500 Date: Mon, 1 Dec 2008 11:40:04 -0800 From: Arjan van de Ven To: Andrew Morton Cc: Frederik Deweerdt , arvidjaar@mail.ru, linux-kernel@vger.kernel.org, philipl@overt.org, linux-acpi@vger.kernel.org Subject: Re: [patch] ACPI toshiba: only register rfkill if bt is enabled Message-ID: <20081201114004.731cec86@infradead.org> In-Reply-To: <20081201113052.9e9aae36.akpm@linux-foundation.org> References: <20081029081934.GB26314@gambetta> <20081201113052.9e9aae36.akpm@linux-foundation.org> Organization: Intel X-Mailer: Claws Mail 3.6.0 (GTK+ 2.14.4; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1447 Lines: 42 On Mon, 1 Dec 2008 11:30:52 -0800 Andrew Morton wrote: > This patch: > > On Wed, 29 Oct 2008 08:19:34 +0000 > Frederik Deweerdt 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 > 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 ". 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/