Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760620AbYHORD0 (ORCPT ); Fri, 15 Aug 2008 13:03:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755642AbYHORDS (ORCPT ); Fri, 15 Aug 2008 13:03:18 -0400 Received: from mail-gx0-f16.google.com ([209.85.217.16]:45679 "EHLO mail-gx0-f16.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755312AbYHORDR (ORCPT ); Fri, 15 Aug 2008 13:03:17 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=wUYd0oJ81tSd633rqO7eE5FmQ4BvehueEbkbKGWlZEXaeHW7LWvsNS9B7vg9eDPbi2 +zmroPYX19Twtgiz0By854D5ySoFFCXFx2Q29uzn9S9b4Be9Ybs4MrWxYjLaw8qgQTq4 wVRxz5HmVe6PmOiGlhLKePd5bs2vMu+oxebYg= Message-ID: Date: Fri, 15 Aug 2008 10:03:16 -0700 From: "Tim Hockin" To: "Greg KH" Subject: Re: [patch 1/3] kmsg: Kernel message catalog macros. Cc: "Joe Perches" , schwidefsky@de.ibm.com, linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, lf_kernel_messages@lists.linux-foundation.org, "Andrew Morton" , "Michael Holzheu" , "Gerrit Huizenga" , "Randy Dunlap" , "Jan Kara" , "Pavel Machek" , "Sam Ravnborg" , "=?UTF-8?Q?Jochen_Vo=C3=9F?=" , "Kunai Takashi" , "Tim Bird" In-Reply-To: <20080815160355.GD23720@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080730165656.118280544@de.ibm.com> <20080730171156.824640459@de.ibm.com> <1218733457.2651.11.camel@localhost> <1218769739.24527.76.camel@localhost> <20080815034419.GB803@suse.de> <20080815160355.GD23720@suse.de> X-Google-Sender-Auth: 7fb6e3c622e8c484 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 989 Lines: 20 On Fri, Aug 15, 2008 at 9:03 AM, Greg KH wrote: >> I'd like to be able to report something like an OOM kill in (roughly) >> the same way as an ATA error, and I want (though could be talked out >> of) a way to tell these "events" (for lack of a better word) apart >> from plain-old-printk()s. > > That's great, then create something that can handle both! Don't throw > away some wonderful information that way over half the kernel has access > to just because the minority doesn't. That would mean that we would > loose information in those drivers overall. Sorry, I never meant to imply that dev_printk() was to be ignored, my examples was meant to be trivial to demonstrate :) dev_printk() is good. We should keep it :) -- 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/