From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262725AbTJTSFZ (ORCPT ); Mon, 20 Oct 2003 14:05:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262726AbTJTSFY (ORCPT ); Mon, 20 Oct 2003 14:05:24 -0400 Received: from adsl-63-194-133-30.dsl.snfc21.pacbell.net ([63.194.133.30]:60804 "EHLO penngrove.fdns.net") by vger.kernel.org with ESMTP id S262725AbTJTSFW (ORCPT ); Mon, 20 Oct 2003 14:05:22 -0400 From: John Mock To: linux-kernel@vger.kernel.org Subject: re: Kill unneccessary debug printk Message-Id: Date: Mon, 20 Oct 2003 11:05:32 -0700 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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. I'm also fine with flushing it that if there's another reasonably convenient way of obtaining the same information. -- JM