From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752685AbdJ3PR4 (ORCPT ); Mon, 30 Oct 2017 11:17:56 -0400 Received: from mga09.intel.com ([134.134.136.24]:39214 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752449AbdJ3PRy (ORCPT ); Mon, 30 Oct 2017 11:17:54 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,320,1505804400"; d="scan'208";a="915448707" From: Jani Nikula To: Matthew Wilcox , Masahiro Yamada Cc: Jonathan Corbet , "open list\:DOCUMENTATION" , Linux Kernel Mailing List , Michal Marek , Linux Kbuild mailing list , Matthew Wilcox Subject: Re: [PATCH] Check all .c files for bad kernel-doc comments In-Reply-To: <20171030134007.GA2846@bombadil.infradead.org> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20171027194149.14328-1-willy@infradead.org> <20171030134007.GA2846@bombadil.infradead.org> Date: Mon, 30 Oct 2017 17:19:18 +0200 Message-ID: <87mv48fytl.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 Mon, 30 Oct 2017, Matthew Wilcox wrote: > On Mon, Oct 30, 2017 at 12:40:20PM +0900, Masahiro Yamada wrote: >> 2017-10-28 4:41 GMT+09:00 Matthew Wilcox : >> > Implement a '-none' output mode for kernel-doc which will only output >> > warning messages, and suppresses the warning message about there being >> > no kernel-doc in the file. Add it to the rule to build .o files from .c >> > files, so it will check all .c files that have been modified. >> > >> > Adds about 1300 warnings to my build, but will hopefully discourage >> > people from introducing more kerneldoc mistakes. >> >> Basically, I think this is good, >> but it is controversial to sprinkle warnings by default. > > Yes, it is. I just got three nastygrams from 01.org ;-) > > But if it's not turned on by default, then people aren't going to notice > when they introduce new warnings. I think it needs to be up to someone > like Andrew or Linus to decide when to add these warnings by default. > Maybe we should do something like you have below for now, then work on > cleaning up a few hundred of these warnings, then enable this by default? > > Thanks for looking at this! > >> Maybe, >> >> ifeq ($(KBUILD_ENABLE_EXTRA_GCC_CHECKS),) >> cmd_checkdoc = $(srctree)/scripts/kernel-doc -none $< ; >> endif >> >> >> so that this is checked only when W=... is given? Related, there was also a script to do reStructuredText lint style checks in addition to the kernel-doc checks using make CHECK and C=1. See [1]. BR, Jani. [1] http://mid.mail-archive.com/87h98quc1w.fsf@intel.com > -- > To unsubscribe from this list: send the line "unsubscribe linux-doc" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jani Nikula, Intel Open Source Technology Center