Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269994AbTGUM5b (ORCPT ); Mon, 21 Jul 2003 08:57:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270014AbTGUM5b (ORCPT ); Mon, 21 Jul 2003 08:57:31 -0400 Received: from fw.osdl.org ([65.172.181.6]:62417 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S269994AbTGUM53 (ORCPT ); Mon, 21 Jul 2003 08:57:29 -0400 Date: Mon, 21 Jul 2003 06:16:34 -0700 (PDT) From: Patrick Mochel X-X-Sender: mochel@cherise To: Ian Soboroff cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.0-test1 - device_suspend KERN_EMERG message? In-Reply-To: <9cffzl0nia3.fsf@rogue.ncsl.nist.gov> 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: 589 Lines: 23 > Is there any special reason to scream that we're suspending devices in > device_suspend? > > int device_suspend(u32 state, u32 level) > { > struct device * dev; > int error = 0; > > printk(KERN_EMERG "Suspending devices\n"); Hey, it's so everyone notices. :) I don't mind toning it down or removing it. -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/