From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933209AbcIVNGS (ORCPT ); Thu, 22 Sep 2016 09:06:18 -0400 Received: from mga11.intel.com ([192.55.52.93]:32793 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755105AbcIVNGO (ORCPT ); Thu, 22 Sep 2016 09:06:14 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,378,1470726000"; d="scan'208";a="12100066" From: Jani Nikula To: Jean Delvare Cc: Joe Perches , Julia Lawall , Al Viro , Ilya Dryomov , Andy Whitcroft , Linus Torvalds , Jonathan Corbet , Ceph Development , Alex Elder , Sage Weil , LKML , kernel-janitors@vger.kernel.org, Andrew Morton , linux-doc@vger.kernel.org Subject: Re: "CodingStyle: Clarify and complete chapter 7" in docs-next In-Reply-To: <20160922144648.10efc7ac@endymion> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20160920001159.GM2356@ZenIV.linux.org.uk> <1474339566.1954.25.camel@perches.com> <1474353123.1954.28.camel@perches.com> <20160922112407.47da9393@endymion> <8760pop63l.fsf@intel.com> <20160922144648.10efc7ac@endymion> User-Agent: Notmuch/0.22.1+62~g2a7b11b (https://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Thu, 22 Sep 2016 16:06:00 +0300 Message-ID: <87zin0nkxz.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 22 Sep 2016, Jean Delvare wrote: > Hi Jani, > > On Thu, 22 Sep 2016 13:43:42 +0300, Jani Nikula wrote: >> >> You could make checkpatch have different defaults for patches and files, >> to encourage better style in new code, but to discourage finding >> problems in existing code. > > Fixing old code isn't wrong per se. It's good actually. But only if > done the right way by the right person. I don't think it makes any > sense to use this task as an introduction to kernel development for > newcomers. It doesn't teach them anything about the kernel, really. Mostly agreed, though I'd go as far as saying certain classes of (checkpatch) issues aren't worth fixing, at all, by anyone, except perhaps while changing the code anyway for some other purpose. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center