From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261776AbTJWUJn (ORCPT ); Thu, 23 Oct 2003 16:09:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261782AbTJWUIc (ORCPT ); Thu, 23 Oct 2003 16:08:32 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.31.123]:12231 "EHLO atrey.karlin.mff.cuni.cz") by vger.kernel.org with ESMTP id S261786AbTJWUIO (ORCPT ); Thu, 23 Oct 2003 16:08:14 -0400 Date: Thu, 23 Oct 2003 22:00:22 +0200 From: Pavel Machek To: John Mock Cc: linux-kernel@vger.kernel.org Subject: Re: Kill unneccessary debug printk Message-ID: <20031023200022.GI643@openzaurus.ucw.cz> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi! > Actually, that 'printk' is useful. As i understand it, the only way software > suspend is going to work is that if the same video mode is used on resume as > on booting. If one uses "vga=ask", then one can 'dmesg | grep' to generate > a proper string for 'lilo -R' (which i already do to make sure the correct > kernel gets resumed during testing). If i'm mistaken about needing to set > VGA mode identically on resume, then i have no objection to removing the > printk. Oops, someone is using my debug printk :-(. I'll at least try to merge it with some other msg, so it does not waste full line. -- Pavel Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...