From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 30 Jul 2008 02:23:54 -0700 From: Andrew Morton Subject: Re: [patch 01/15] kmsg: Kernel message catalog macros. Message-Id: <20080730022354.76034424.akpm@linux-foundation.org> In-Reply-To: <1217409221.11260.3.camel@localhost> References: <20080728175355.734299984@de.ibm.com> <20080728175511.023246676@de.ibm.com> <20080730013059.4d411750.akpm@linux-foundation.org> <1217409221.11260.3.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-Archive: List-Post: To: schwidefsky@de.ibm.com Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, Michael Holzheu List-ID: On Wed, 30 Jul 2008 11:13:41 +0200 Martin Schwidefsky wrote: > On Wed, 2008-07-30 at 01:30 -0700, Andrew Morton wrote: > > On Mon, 28 Jul 2008 19:53:56 +0200 Martin Schwidefsky wrote: > > Numerous people want a facility like this for other-than-s390 use. > > Progress has been intermittent and appears to have stopped. The > > apparently-dead mailing list is archived here: > > https://lists.linux-foundation.org/pipermail/lf_kernel_messages/. > > > > I don't know what the future holds for that development effort, but the > > requirement won't go away. So one day someone is going to go and yank > > your implementation out of arch/s390 and into generic code. > > > > So I'd suggest that you start out that way. > > Somehow I have hoped for an answer like that :-) The only thing that > we'd have to do is find a proper place for the kmsg header file, > include/linux/kmsg.h comes to mind. The kmsg-doc script can easily be > change to check for multiple documentation directories, I was thinking > about Documentation/kmsg/$ARCH for the architecture specific things and > Documentation/kmsg for the generic parts. > No objections from me. It would be wonderful if someone could troll those list archives and see if they can wake up the people who were involved in that effort. They probably won't help much with development but it would be useful if we could get their review/design input.