Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 21 Oct 2002 13:03:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 21 Oct 2002 13:03:55 -0400 Received: from air-2.osdl.org ([65.172.181.6]:47744 "EHLO cherise.pdx.osdl.net") by vger.kernel.org with ESMTP id ; Mon, 21 Oct 2002 13:03:54 -0400 Date: Mon, 21 Oct 2002 10:13:12 -0700 (PDT) From: Patrick Mochel X-X-Sender: mochel@cherise.pdx.osdl.net To: "Eric W. Biederman" cc: "Adam J. Richter" , , , Russell King Subject: Re: Patch: linux-2.5.42/kernel/sys.c - warm reboot should not suspend devices In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 725 Lines: 18 > Question, is there a method from the class shutdown code that we > can/should call, during reboot. I just have this memory that for > network interfaces simply downing the interface tends to put it in > a quiescent state. And I am wondering if that might be a general > thing we can take advantage of. Though if the class remove methods > modify the data structures I guess that is out. No. Bringing down the network interface, at least, can be done from userspace. -pat - 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/