From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263672AbTDTSml (ORCPT ); Sun, 20 Apr 2003 14:42:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263673AbTDTSmk (ORCPT ); Sun, 20 Apr 2003 14:42:40 -0400 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:9428 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id S263672AbTDTSmj (ORCPT ); Sun, 20 Apr 2003 14:42:39 -0400 Message-ID: <3EA2ECE5.2050100@pobox.com> Date: Sun, 20 Apr 2003 14:54:29 -0400 From: Jeff Garzik Organization: none User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021213 Debian/1.2.1-2.bunk X-Accept-Language: en MIME-Version: 1.0 To: Andries.Brouwer@cwi.nl CC: torvalds@transmeta.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH] silence some superfluous boot messages References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Andries.Brouwer@cwi.nl wrote: > I suppose these can be removed altogether. > For now #if 0 ... #endif. would it not be preferable to mark these as KERN_DEBUG instead? Sure they will still show up in dmesg, but that gives the code authors opportunity to themselves adjust the messages, mark them as DPRINTK(), or #if-0 them out themselves. Jeff