From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [linux-pm] [RFC][PATCH 3/3] PM: Remove PM_TRACE from Kconfig Date: Thu, 17 Aug 2006 11:12:38 +0200 Message-ID: <20060817091238.GA17899@elf.ucw.cz> References: <200608151509.06087.rjw@sisk.pl> <20060816104143.GC9497@elf.ucw.cz> <200608161304.51758.rjw@sisk.pl> <200608161314.11128.rjw@sisk.pl> <20060817044011.GB14127@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20060817044011.GB14127@kroah.com> Sender: linux-kernel-owner@vger.kernel.org To: Greg KH Cc: "Rafael J. Wysocki" , Linux PM , LKML List-Id: linux-pm@vger.kernel.org Hi! > > Remove the CONFIG_PM_TRACE option, which is dangerous and should only be used > > by people who know exactly what they are doing, from Kconfig. > > No, don't remove this, that's not acceptable at all. This is useful for > others (and one specifically who will be pissed to see this removed...) Yep, while it breaks suspend for every pool soul that enables it by mistake. (And in hard-to-debug way, too). This option has EXACTLY ONE USER... or more precisely used to have one user when he was debugging his mac mini... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html