Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756697AbZD2MBY (ORCPT ); Wed, 29 Apr 2009 08:01:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755567AbZD2MBO (ORCPT ); Wed, 29 Apr 2009 08:01:14 -0400 Received: from cantor.suse.de ([195.135.220.2]:58547 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755363AbZD2MBN (ORCPT ); Wed, 29 Apr 2009 08:01:13 -0400 Date: Wed, 29 Apr 2009 14:01:12 +0200 (CEST) From: Jiri Kosina X-X-Sender: jkosina@wotan.suse.de To: "Robert P. J. Day" Cc: Johannes Weiner , Linux Kernel Mailing List Subject: Re: how to properly post/disseminate kernel cleanup/janitorial possibilities? In-Reply-To: Message-ID: References: <20090427222035.GA2700@cmpxchg.org> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) 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: 1025 Lines: 23 On Tue, 28 Apr 2009, Robert P. J. Day wrote: > > > Perhaps Jiri can pick up some of the patches that remove stale > > > config symbols, correct typos etc. > > Absolutely. I'll happily apply anything trivial enough (typo fixes, > > removal of obviously unused symbols/config options, etc). > the *problem* is that, sometimes, it's not obvious. as in, when a > Kconfig file has a pile of unused config options but it turns out that > those were added for future consideration to match up with code that > hasn't been added yet and the subsystem maintainer knows about it but > wants it to stay (IMHO, a really bad idea -- adding kernel features in > incomplete pieces, but whatever). Hmm ... do you have any particular outstanding examples of this? -- Jiri Kosina SUSE Labs -- 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/