Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp522284pxv; Wed, 14 Jul 2021 09:11:40 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzIS3C8b+xGIySBLSYWqpiAlxjbj2XQ9DEGn/nBNejJanobMFyODpKpsJKFqv49TQ8uIB9t X-Received: by 2002:aa7:d157:: with SMTP id r23mr14720606edo.127.1626279100213; Wed, 14 Jul 2021 09:11:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626279100; cv=none; d=google.com; s=arc-20160816; b=YsYqZrbYqnZhy/xQ4KkntdPt2W6yd+ttxfVa99XNURMG1iVWyafW/0dXSvYgnIjpeA yrQHyyiHU0i/TqnnNw83M6cHZmMPvwiIFGlYqBPMRuWIDOgwV60QoRGZi9x66/jiu+fe oPo5WktFkHGYeOhkI5aF5om5HjEf1Qkeq4sXXaQbvQa8JBIML4VWyL0RtyCjWdQ8aqUS cbMp9MwZo8ifdcD6rxHxThll50xClJjTgfs2HuijS9YNGkr3PTtyFG7tMRk0RipT2BtN DQbT4YJqGmmhLE6hujFKMsEO/Jmgj5CmLbXQ+Fhj+wCk7TgdeSBhyFnm/cjmch7/RiBB 3Uzw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=aO437vaP/6XkwDCzV+aicwQ9UhYHgRxCHc2jjBDtvpg=; b=rx4aR0eyfrBIkZYYhhZUeXHx0lrwS34CZTl4vpiZeyReOVAPuNbkUa3QfAWUaU+ICS 4RPg7ijrum63cvJ4moYM+bT85hIEKDlBQBIVLw4bP9rTYBJQyDhx+icTswMnvBlsgmmc NFpmvZ66EgQxLgFxSxYSmm0EW03u7plHhQLL4KtBpBWrSrZYjHzJBQqqGCmdJxqlVe2W 2ezgo55C9m/kr6wXJkEgAmiUEz+dnUrmXTh6k0518iiIh5cIaL/26Yy9nmX603R90fwZ bDhaqN72eTuQ920/qzRO4tS3OSfPdas4bGZuDLiMMHRoJPytQ8ywnkxeTZbOALF1g9jE zY3Q== 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 ee47si3283901edb.7.2021.07.14.09.11.17; Wed, 14 Jul 2021 09:11:40 -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 S231941AbhGNQJ6 (ORCPT + 99 others); Wed, 14 Jul 2021 12:09:58 -0400 Received: from foss.arm.com ([217.140.110.172]:36544 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230427AbhGNQJ6 (ORCPT ); Wed, 14 Jul 2021 12:09:58 -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 35334D6E; Wed, 14 Jul 2021 09:07:06 -0700 (PDT) Received: from e120937-lin (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 7669C3F7D8; Wed, 14 Jul 2021 09:07:04 -0700 (PDT) Date: Wed, 14 Jul 2021 17:07:02 +0100 From: Cristian Marussi To: Sudeep Holla Cc: "Rafael J. Wysocki" , ACPI Devel Maling List , Linux Kernel Mailing List , "Rafael J . Wysocki" , Jassi Brar Subject: Re: [PATCH 02/13] ACPI: CPPC: Fix doxygen comments Message-ID: <20210714160702.GB6592@e120937-lin> References: <20210708180851.2311192-1-sudeep.holla@arm.com> <20210708180851.2311192-3-sudeep.holla@arm.com> <20210714151210.or4kburfmcsjo3u2@bogus> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210714151210.or4kburfmcsjo3u2@bogus> User-Agent: Mutt/1.9.4 (2018-02-28) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > -- > Regards, > Sudeep