Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp528867pxv; Wed, 14 Jul 2021 09:18:11 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwQe4uE3yq94//sVVDN3nJ8tqwRw7gFQ6lH9NpHjpXFONHYht0bDl24x2FYbyC2nKM0qSgi X-Received: by 2002:a17:906:4dc5:: with SMTP id f5mr13398636ejw.162.1626279491100; Wed, 14 Jul 2021 09:18:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626279491; cv=none; d=google.com; s=arc-20160816; b=Su4BN/k8T8oEUXL9BTHSwhaqJwKP3Q8fomy18MKypDIjCzc9AaIe0BkPMQ9Xm52Z2U OSklriBV1ixb5tWIw4d05QymeaGar6bgDPIOS0q6Xe4E0jqVP9n1cl9Kh7vArYek6ORN eqR9gGBsYWvJcAOYZUntO3y1Dgvmste6SHBK20ma1uVEK+c2yZTp2BpCYD/+iZlaVqMB goxywqXm9kYcWpsSHu3x0tCdyMGd3wt65QJLoALEgt/6TL0QEPd3lfQmFnjsqzXAkd0k mT1eJX1QRtoCotqklb7q9Oel/NE0/PNcIkx6x0yyVVAicd2IOeAXMOBc4vWm0INkbnR5 JPjw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=IXQmgWuVhpQ2FFN1unCeWn6FYqhjOXSIJDq/WUNVPp4=; b=KiG97jVczFF+AJJLx7LCYB6MLZ6dUeGpq9vqSlpcDwSDwZiYjyQ8XlfWzRr7alkFSy gFjqJNjDlQJYFEVQVINMom+V8nrMgzcThisdq3kGVkIzaCQTlp67scGfEc5hCfB7EOzZ dXFEznEdDUQhbrHkSjGq0wOHQArsx13pKyc2gG8i9Zs0rNbHx4hrzAfluxb8ZXOQ/n1x McPgtc1Gw+yysaH5uiOROsE46jAbmgt8e9yAck4a2AxGapxVgkPYXeiuotsSbyGwByLN nw1vkDTPQyXd6bZp8eHk0jTfpiArie3HCaE4b2FWlm9Yd6K7atdENH7yPdx0+e/obnzf Enjg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id mc17si3060749ejb.622.2021.07.14.09.17.45; Wed, 14 Jul 2021 09:18:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235708AbhGNQS1 (ORCPT + 99 others); Wed, 14 Jul 2021 12:18:27 -0400 Received: from foss.arm.com ([217.140.110.172]:36670 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230427AbhGNQS1 (ORCPT ); Wed, 14 Jul 2021 12:18:27 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 3B7F5D6E; Wed, 14 Jul 2021 09:15:35 -0700 (PDT) Received: from bogus (unknown [10.57.79.213]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 14AA03F7D8; Wed, 14 Jul 2021 09:15:33 -0700 (PDT) Date: Wed, 14 Jul 2021 17:14:35 +0100 From: Sudeep Holla To: Cristian Marussi Cc: "Rafael J. Wysocki" , ACPI Devel Maling List , Linux Kernel Mailing List , "Rafael J . Wysocki" , Sudeep Holla , Jassi Brar Subject: Re: [PATCH 02/13] ACPI: CPPC: Fix doxygen comments Message-ID: <20210714161435.fp6z6wqvmvobynwm@bogus> References: <20210708180851.2311192-1-sudeep.holla@arm.com> <20210708180851.2311192-3-sudeep.holla@arm.com> <20210714151210.or4kburfmcsjo3u2@bogus> <20210714160702.GB6592@e120937-lin> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210714160702.GB6592@e120937-lin> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 14, 2021 at 05:07:02PM +0100, Cristian Marussi wrote: > On Wed, Jul 14, 2021 at 04:12:10PM +0100, Sudeep Holla wrote: > > On Wed, Jul 14, 2021 at 02:20:05PM +0200, Rafael J. Wysocki wrote: > > > On Thu, Jul 8, 2021 at 8:09 PM Sudeep Holla wrote: > > > > > > > > Clang complains about doxygen comments too with W=1 in the build. > > > > > > > > | drivers/acpi/cppc_acpi.c:560: warning: Function parameter or member > > > > | 'pcc_ss_id' not described in 'pcc_data_alloc' > > > > | drivers/acpi/cppc_acpi.c:1343: warning: Function parameter or member > > > > | 'cpu_num' not described in 'cppc_get_transition_latency' > > > > > > > > Fix it. > > > > > > > > Signed-off-by: Sudeep Holla > > > > --- > > > > drivers/acpi/cppc_acpi.c | 7 +++++++ > > > > 1 file changed, 7 insertions(+) > > > > > > > > diff --git a/drivers/acpi/cppc_acpi.c b/drivers/acpi/cppc_acpi.c > > > > index a4d4eebba1da..eb5685167d19 100644 > > > > --- a/drivers/acpi/cppc_acpi.c > > > > +++ b/drivers/acpi/cppc_acpi.c > > > > @@ -562,6 +562,8 @@ bool __weak cpc_ffh_supported(void) > > > > /** > > > > * pcc_data_alloc() - Allocate the pcc_data memory for pcc subspace > > > > * > > > > > > I would drop this empty line (and analogously below). > > > > > > > Sure > > > > > > + * @pcc_ss_id: PCC Subspace channel identifier > > > > + * > > > > * Check and allocate the cppc_pcc_data memory. > > > > * In some processor configurations it is possible that same subspace > > > > * is shared between multiple CPUs. This is seen especially in CPUs > > > > @@ -1347,10 +1349,15 @@ EXPORT_SYMBOL_GPL(cppc_set_perf); > > > > /** > > > > * cppc_get_transition_latency - returns frequency transition latency in ns > > > > * > > > > + * @cpu_num: Logical index of the CPU for which latencty is requested > > > > + * > > > > * ACPI CPPC does not explicitly specify how a platform can specify the > > > > * transition latency for performance change requests. The closest we have > > > > * is the timing information from the PCCT tables which provides the info > > > > * on the number and frequency of PCC commands the platform can handle. > > > > + * > > > > + * Returns: frequency transition latency on success or CPUFREQ_ETERNAL on > > > > + * failure > > > > > > Is this change needed? The one-line summary already says this. > > > > > > > Right, not required. I must have got confused with other place that expected > > return summary. > > > I think kernel-doc complains if no Return: (not Returns:) doxygen clause > is provided while describing a function which do return some values. > (..even though the info is clearly duplicated as it is now in the > one-line summary) > Thanks Cristian, just noticed the same. I was convinced that I did see the warning before but couldn't recollect the details quickly. $ ./scripts/kernel-doc -none drivers/acpi/cppc_acpi.c (no warnings) $ ./scripts/kernel-doc -v -none drivers/acpi/cppc_acpi.c drivers/acpi/cppc_acpi.c:1345: warning: No description found for return value of 'cppc_get_transition_latency' The build with W=1 may not be using -v. That explains why I got confused as I initially started with W=1 build but did switch to ./scripts/kernel-doc -v after Joe pointed out its existence. -- Regards, Sudeep