Received: by 10.223.185.116 with SMTP id b49csp3157367wrg; Sun, 18 Feb 2018 15:49:19 -0800 (PST) X-Google-Smtp-Source: AH8x2240HLCScy0sBZb5zZpXTZC/7CwrkInRyKhoYGx9XC4SQAoSh8LFxuYzKc7jeOmurDZB8Wrz X-Received: by 2002:a17:902:4222:: with SMTP id g31-v6mr12182030pld.335.1518997759779; Sun, 18 Feb 2018 15:49:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518997759; cv=none; d=google.com; s=arc-20160816; b=nm7g3TLDRJgYwRAmbe38a0Mop1BSAz5b+Xkgq/JIkf3zSMVf08RJE9nPD/wZSUPS9w qDo1AwhYuWw2nzR/S16px/nmwMm7K2mUjRzBpPxKNDUNrqYi5qGlxWysv8aCbKtYiDjc ALUDqilyHUoSyxEGc8YuiqDtSCqYNAaE747s9rbPdszKE5IG9Ruy+ugRsqXc/NqgoHGI 6JLAyWRdA8SrjyYFOr2EkZFwnhHMPGg6it7d2mVoOugmQ5M5aF+pZXQ1XEw3oJRZyYW9 Uu57dYFXL3c1tCRkrWO+AxwH4v2RaTjVRymTMSs7ClwqyQj3kDpcz1zrVrdfpECehon7 gDiQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:arc-authentication-results; bh=IIYAmtJfgxF7rmX+c5L8vSfT3Cwe7SN871U1yTNE0Cc=; b=pJJUpgHQBK0epdzkTz/RVXpJ8wpyCwFHgSjnw7qT93AiToyOrfsvYkzqjX0KbIUCnw N687lSU2oFMr2ijIuEFf+eDhSW0+XYXM20yyP7Wii9nphJ6Iltpib+ItL+6Kv/n62u3m 9WuBgQWpxFVnnUiA6SRQSKLcnAfHDa4pEqJ+qBzXQtVhhHYx4IsYuL+/HkfRSzxEKNYo 6NwnV2W5LKA451dtFHEfgKrjComytbUu1hpKyBjmiau7b6HCqGWH9ZHnJ2zpPn3ihelD xSgwJg4UTqD6ko4sjaBPSLghisu/tgckpF3gkUU8EOyr70RMmuNWowS3tMi1YQBs7pT9 0bjQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m1-v6si1547772plt.295.2018.02.18.15.49.05; Sun, 18 Feb 2018 15:49:19 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751910AbeBRXs2 (ORCPT + 99 others); Sun, 18 Feb 2018 18:48:28 -0500 Received: from ms.lwn.net ([45.79.88.28]:52152 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751733AbeBRXs1 (ORCPT ); Sun, 18 Feb 2018 18:48:27 -0500 Received: from localhost.localdomain (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 95BE54B7; Sun, 18 Feb 2018 23:48:21 +0000 (UTC) Date: Sun, 18 Feb 2018 16:48:05 -0700 From: Jonathan Corbet To: Markus Heiser Cc: Mike Rapoport , Linux Doc Mailing List , linux-kernel@vger.kernel.org Subject: Re: [PATCH] scripts: kernel_doc: fixup reporting of function identifiers Message-ID: <20180218164805.2cf46459@lwn.net> In-Reply-To: <17062CC8-55BF-423B-A4F5-726291417D21@darmarit.de> References: <1518521506-6770-1-git-send-email-rppt@linux.vnet.ibm.com> <20180216075642.2e56eb51@lwn.net> <17062CC8-55BF-423B-A4F5-726291417D21@darmarit.de> Organization: LWN.net X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 16 Feb 2018 17:36:07 +0100 Markus Heiser wrote: > > So let me channel akpm here and ask: what are the user-visible effects of > > this problem? I ask because applying it doesn't make any difference in > > the "make htmldocs" output here. So I don't understand why you're > > wanting to make this change. > > Use kernel-doc -v and take a look on the info-messages. > > In Documentation/doc-guide/kernel-doc we recommend to use > > /** > * foo() - lorem ipsum > > to tag functions, but if you do so, the info message is broken, > the function name is missed at the end of the message: > > ../test123.c:2: info: Scanning doc for OK, so I guess that message is the only effect of this bug. Oh well, I'll go ahead and apply the patch, thanks. jon