From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752248AbaCHVCS (ORCPT ); Sat, 8 Mar 2014 16:02:18 -0500 Received: from cpsmtpb-ews01.kpnxchange.com ([213.75.39.4]:49500 "EHLO cpsmtpb-ews01.kpnxchange.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751716AbaCHVCQ (ORCPT ); Sat, 8 Mar 2014 16:02:16 -0500 Message-ID: <1394312534.2040.18.camel@x220> Subject: Re: [PATCH] [RESEND] score: remove unused CPU_SCORE7 Kconfig parameter From: Paul Bolle To: Lennox Wu Cc: Michael Opdenacker , open list Date: Sat, 08 Mar 2014 22:02:14 +0100 In-Reply-To: References: <1386567192-19924-1-git-send-email-michael.opdenacker@free-electrons.com> <1394256390-10603-1-git-send-email-michael.opdenacker@free-electrons.com> <1394308828.431.5.camel@x220> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-2.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 08 Mar 2014 21:02:15.0324 (UTC) FILETIME=[AEFB95C0:01CF3B11] X-RcptDomain: vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2014-03-09 at 04:27 +0800, Lennox Wu wrote: > 2014-03-09 4:00 GMT+08:00 Paul Bolle : > > In https://lkml.org/lkml/2011/11/12/76 I already reported that this > > Kconfig symbol was unused. Why can't it be dropped and re-added when > > code is added to the tree that actually uses it? > > Because I don't think droping it is meaningful, since it will be used. But, again, it isn't used now and hasn't actually been used in years. > Moreover, the symbol never affect other architectures or subsystems. > I feel that is not good to brother people to process the unimportant patch. Sure, this is just a small cleanup. But the scripts people use to see whether more serious Kconfig related issues have entered the tree will likely notice CPU_SCORE7. (And those people will have to investigate why that symbol is unused - which might take quite a bit of work - to determine what needs to be done about it.) So whenever someone, not following this thread, runs a script like that the score maintainers might receive a similar patch again. And I don't believe that handling a single cleanup patch is particularly burdensome for the score maintainers. Paul Bolle