From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756478AbdGXVcH (ORCPT ); Mon, 24 Jul 2017 17:32:07 -0400 Received: from ms.lwn.net ([45.79.88.28]:39022 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752020AbdGXVcA (ORCPT ); Mon, 24 Jul 2017 17:32:00 -0400 Date: Mon, 24 Jul 2017 15:31:58 -0600 From: Jonathan Corbet To: Randy Dunlap Cc: Andrew Morton , LKML , linux-doc@vger.kernel.org Subject: Re: [PATCH] kthread: Fix documentation build warning Message-ID: <20170724153158.5c5c8bb2@lwn.net> In-Reply-To: <565b9218-e74d-7a9e-01c8-9c614a6d430f@infradead.org> References: <20170724135916.7f486c6f@lwn.net> <565b9218-e74d-7a9e-01c8-9c614a6d430f@infradead.org> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 24 Jul 2017 14:24:44 -0700 Randy Dunlap wrote: > > + * @arg...: arguments for @namefmt. > > * > > Hm, Documentation/doc-guide/kernel-doc.rst says: > If a function parameter is ``...`` (varargs), it should be listed > in kernel-doc notation as: ``@...:``. > > but the patch here is for a macro, not a function. > Does that make a difference? Macros are a little different. I've tried a couple of times to figure out and rationalize the "..." handling, should maybe do so again. Meanwhile, this makes the warning go away, enough for one day :) Thanks, jon