Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932648AbYB2XLl (ORCPT ); Fri, 29 Feb 2008 18:11:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755741AbYB2XLb (ORCPT ); Fri, 29 Feb 2008 18:11:31 -0500 Received: from sovereign.computergmbh.de ([85.214.69.204]:41632 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755620AbYB2XLa (ORCPT ); Fri, 29 Feb 2008 18:11:30 -0500 Date: Sat, 1 Mar 2008 00:11:28 +0100 (CET) From: Jan Engelhardt To: Krzysztof Halasa cc: linux-kernel@vger.kernel.org Subject: Re: Few ideas... In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 869 Lines: 21 On Feb 29 2008 23:48, Krzysztof Halasa wrote: >Hi, > >There was a thread about MODULE_MAINTAINER but how about a tag which >a) would be present in source files, not necessarily one per module >c) would be machine-parseable >d) would have _no_ effect on object code (i.e., would be ignored by > the compiler completely)? d: I think it would not bad if it were included in the resulting object file like MODULE_AUTHOR is. If anything, MODULE_AUTHOR could be removed, because the original author(s) are usually listed at the top of the .c file and not always the ones to talk to when there is a bug (=> the maintainer is). -- 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/