From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D78AAC10F14 for ; Tue, 15 Oct 2019 13:18:49 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 815F621D7D for ; Tue, 15 Oct 2019 13:18:48 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 815F621D7D Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 2CF5C8E0005; Tue, 15 Oct 2019 09:18:48 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 27F808E0001; Tue, 15 Oct 2019 09:18:48 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 195E68E0005; Tue, 15 Oct 2019 09:18:48 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0228.hostedemail.com [216.40.44.228]) by kanga.kvack.org (Postfix) with ESMTP id E6F7A8E0001 for ; Tue, 15 Oct 2019 09:18:47 -0400 (EDT) Received: from smtpin25.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with SMTP id 3B735181AEF1E for ; Tue, 15 Oct 2019 13:18:47 +0000 (UTC) X-FDA: 76046073894.25.toy13_4c914355f6f41 X-HE-Tag: toy13_4c914355f6f41 X-Filterd-Recvd-Size: 2659 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by imf43.hostedemail.com (Postfix) with ESMTP for ; Tue, 15 Oct 2019 13:18:45 +0000 (UTC) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Oct 2019 06:18:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.67,300,1566889200"; d="scan'208";a="208181089" Received: from mcretu-mobl.ger.corp.intel.com (HELO localhost) ([10.252.56.150]) by fmsmga001.fm.intel.com with ESMTP; 15 Oct 2019 06:18:38 -0700 From: Jani Nikula To: Matthew Wilcox , Thomas Zimmermann Cc: Tim.Bird@sony.com, changbin.du@gmail.com, corbet@lwn.net, linux-doc@vger.kernel.org, linux-pci@vger.kernel.org, linux-fpga@vger.kernel.org, linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-mm@kvack.org, linux-crypto@vger.kernel.org, linux-kselftest@vger.kernel.org, intel-gfx@lists.freedesktop.org Subject: Re: [PATCH] kernel-doc: rename the kernel-doc directive 'functions' to 'specific' In-Reply-To: <20191015115439.GE32665@bombadil.infradead.org> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20191013055359.23312-1-changbin.du@gmail.com> <875zkrd7nq.fsf@intel.com> <7e7557b5-469f-3e63-6254-53dab2d7234a@suse.de> <20191015115439.GE32665@bombadil.infradead.org> Date: Tue, 15 Oct 2019 16:19:36 +0300 Message-ID: <8736fub0yf.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue, 15 Oct 2019, Matthew Wilcox wrote: > On Tue, Oct 15, 2019 at 11:25:53AM +0200, Thomas Zimmermann wrote: >> > My preference would be to use 'symbols'. I tried to come up with something >> > but 'symbols' is better than anything I came up with. >> >> Maybe 'interfaces' or 'artifacts'. The term 'symbols' is just as >> imprecise as 'functions'. > > I suggested 'identifier' because that's the term used in the C spec (6.2.1): > > : An identifier can denote an object; a function; a tag or a member > : of a structure, union, or enumeration; a typedef name; a label name; > : a macro name; or a macro parameter. > > We don't allow documenting all those things separately, but it does cover > all the things we do allow to be individually documented. Agreed. BR, Jani. -- Jani Nikula, Intel Open Source Graphics Center