Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932581AbcDYM5u (ORCPT ); Mon, 25 Apr 2016 08:57:50 -0400 Received: from mailapp01.imgtec.com ([195.59.15.196]:16352 "EHLO mailapp01.imgtec.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932231AbcDYM5t (ORCPT ); Mon, 25 Apr 2016 08:57:49 -0400 Date: Mon, 25 Apr 2016 13:58:09 +0100 From: Eric Engestrom To: Arnd Bergmann CC: , Alexandre Belloni , Nicolas Pitre , Krzysztof Kozlowski , Tony Lindgren , Linus Walleij , Nicolas Ferre , Lee Jones , Roland Stigge , Florian Fainelli , Russell King , Alexander Shiyan , Kevin Hilman , Viresh Kumar , , Jean-Christophe Plagniol-Villard , , Ray Jui , Rajendra Nayak , Sekhar Nori , Krzysztof Halasa , Gregory Fong , , Paul Walmsley , Scott Branden , Shiraz Hashim , , Sascha Hauer , Shawn Guo Subject: Re: [PATCH 4/4] ARM: remove duplicate const qualifier Message-ID: <20160425125809.GP32731@imgtec.com> References: <1461577678-29517-1-git-send-email-eric.engestrom@imgtec.com> <20160425095715.GA2366@piout.net> <20160425103911.GO32731@imgtec.com> <4641918.pNBP5iAK01@wuerfel> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline In-Reply-To: <4641918.pNBP5iAK01@wuerfel> User-Agent: Mutt/1.5.21 (2010-09-15) X-Originating-IP: [10.60.4.28] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 980 Lines: 23 On Mon, Apr 25, 2016 at 01:38:18PM +0200, Arnd Bergmann wrote: > Maybe say you you found it (llvm, sparse, coccinelle?), and why this > is causing a problem for anyone. If it's just unnecessary but not > harmful, I'd probably ignore the patch. $ grep -rE '(^|\W)const(\s+\w+)+\s+const\s' I just happened to notice some unnecessary const in our internal code, so I grep'ed for it in a couple big OSS projects to see how common it was. Since I found only a few, I decided to remove them, but like I said it just gets ignored by all the compilers I know, so there's absolutely no harm in leaving this dead code around. > That's fine. Having multiple patches here is slightly better than just > one, but I'd also be fine with just taking the large patch because it > is an identical trivial change in multiple files. So, do you want me to split them up? I'd prefer not having to (slightly less work for me :P), but it doesn't really make much of a difference either way. Cheers