Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 11 Mar 2002 11:39:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 11 Mar 2002 11:39:31 -0500 Received: from vindaloo.ras.ucalgary.ca ([136.159.55.21]:48562 "EHLO vindaloo.ras.ucalgary.ca") by vger.kernel.org with ESMTP id ; Mon, 11 Mar 2002 11:39:17 -0500 Date: Mon, 11 Mar 2002 09:37:58 -0700 Message-Id: <200203111637.g2BGbww03811@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: vda@port.imtp.ilyichevsk.odessa.ua Cc: linux-kernel@vger.kernel.org, Alan Cox Subject: Re: [PATCH] KERN_INFO 2.4.19-pre2 devfs In-Reply-To: <200203111343.g2BDhRq05326@Port.imtp.ilyichevsk.odessa.ua> In-Reply-To: <200203111343.g2BDhRq05326@Port.imtp.ilyichevsk.odessa.ua> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Denis Vlasenko writes: > Primary purpose of this patch is to make KERN_WARNING and > KERN_INFO log levels closer to their original meaning. > Today they are quite far from what was intended. > Just look what kernel writes at the WARNING level > each time you boot your box! > > Diff for devfs. I've already posted a patch which adds KERN_* to all printk()'s in devfs (devfs-patch-v199.9). I even submitted it to Marcelo, but we were in 2.4.18-rc1 so he deferred it. It's queued for resubmission. Be patient. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca - 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/