Return-path: Received: from mail-wi0-f174.google.com ([209.85.212.174]:51348 "EHLO mail-wi0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753004Ab2ABWT7 (ORCPT ); Mon, 2 Jan 2012 17:19:59 -0500 MIME-Version: 1.0 In-Reply-To: <20120102221235.GA16012@srcf.ucam.org> References: <4F02165C.1060400@fastmail.fm> <20120102211904.GA15316@srcf.ucam.org> <20120102215028.GA15701@srcf.ucam.org> <20120102221235.GA16012@srcf.ucam.org> From: Linus Torvalds Date: Mon, 2 Jan 2012 14:19:37 -0800 Message-ID: (sfid-20120102_232028_864063_221FDDE5) Subject: Re: loading firmware while usermodehelper disabled. To: Matthew Garrett Cc: Jack Stone , Alan Stern , Oliver Neukum , Dave Jones , Linux Kernel , Larry Finger , Chaoming Li , "John W. Linville" , Greg Kroah-Hartman , USB list , Linux Wireless List Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, Jan 2, 2012 at 2:12 PM, Matthew Garrett wrote: > > The kernel that loaded the firmware to make the device work is not > required to be the same kernel that we're running when we suspend. Why do you make up all these idiotic theoretical cases that nobody cares about and has no relevance what-so-ever for the 99%? Seriously? It's just stupid. If you have some multi-kernel setup, or depend on booting windows before booting Linux in order to have the firmware there, or you use hibernate and switch things around (hibernate, not suspend - different thing), and cannot load the firmware in the regular kernel, who the hell cares? And if you *can* load the firmware in the new kernel, just do it before the suspend event. Problem solved. And once more: your made-up scenario has *nothing* what-so-ever to do with the actual warnings that started this whole thread. You seem to *intentionally* be off in some random alternate reality that is not relevant to anybody else, or to the actual reported problems at hand. Why? Linus