Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760652AbYG1R4A (ORCPT ); Mon, 28 Jul 2008 13:56:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758405AbYG1Rz1 (ORCPT ); Mon, 28 Jul 2008 13:55:27 -0400 Received: from mtagate4.de.ibm.com ([195.212.29.153]:62136 "EHLO mtagate4.de.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757983AbYG1Rz0 (ORCPT ); Mon, 28 Jul 2008 13:55:26 -0400 Message-Id: <20080728175355.734299984@de.ibm.com> User-Agent: quilt/0.46-1 Date: Mon, 28 Jul 2008 19:53:55 +0200 From: Martin Schwidefsky To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org Subject: [patch 00/15] [RFC] kmsg macros and script. Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1255 Lines: 30 Greetings, this is the next step of our project to document all s390 specific kernel messages. The message cleanup patches have been integrated into the upstream kernel. After we removed the meaningless messages it is now time to brush up the remaining messages. The first patch introduces a new set of wrapper macros around printk. These macros add a prefix to each message and a message id can be specified. The second patch adds a script to help writing the kmsg comments that describe a kmsg and it can be used to write man pages for the documented messages. The remaining 13 patches convert some of the printk messages found in the s390 architecture files and some of the s390 device drivers to demonstrate how all this is supposed to work. The code is currently only usable for s390. Should this be of interest to other architectures as well we have to think about where to put things. We'd be happy to get feedback on this. -- blue skies, Martin. "Reality continues to ruin my life." - Calvin. -- 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/