From nobody Sun Feb 8 10:05:05 2026 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3E593156F3A for ; Sat, 11 Jan 2025 06:30:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.137.202.133 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736577021; cv=none; b=iF8nt+BPsYZMra9uKJ2INDzGelG56xq7T05yhsOgaLAPWIgquZsrwe0p6TzI6wC5jDxm69pbmuHo1LsZ/4ztLFMIbn24Q5C4Bsrr7y9INwPlLzsE2SHoOasHT+HiEDsdapDq30hepeid7YU2ZHD9EWk94v4PtLl8zbFF3gqT3rE= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736577021; c=relaxed/simple; bh=HlY6ruWyBLkNLf5bupjQITOvFI8DZKDNE6iWtJQ92eU=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=Iq3tfq2VO0DLorABivPbwsEVIfDkMXuX97Z9OjPz3WhGnS2VsimILNe/ldRhojp7OwSg4yxEGD0W5np4yNHKWVWXxeGhpjb3IR0KUFzNht1yFc/KWCO3swUbxx9X7lqrL4w5KqFehnVTQnBMlAOrFkRj4WqfnynFOc1wNBQeCRU= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org; spf=none smtp.mailfrom=infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=RAsaeNme; arc=none smtp.client-ip=198.137.202.133 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=infradead.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="RAsaeNme" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=Content-Transfer-Encoding: MIME-Version:Message-ID:Date:Subject:Cc:To:From:Sender:Reply-To:Content-Type: Content-ID:Content-Description:In-Reply-To:References; bh=4aTUiCiHr4H7yTVa78VaekxBKpVUNCIiwrYN/T8YS1k=; b=RAsaeNmeddumiFirhONv8/i8x0 1VM2oJEU4lh5Cteby5RDHvgzDL+FQZiQhL7+lo6DCPhxI64rfn4IcbuitTXZtqasPeM1F3hbaTA6a i3czhDISNOcVQNuYW94VA/mt7c4O4ex+AXUagicxfjEVR1y/WvtJYaPrPH/039RfnS/JOgD+RyYxd 6QiMeaqwggVJNVQh4rv4+ETdLaMWw8vlk2Y34UPk+Zuh2SKUpfeo64H2kMHwTfD5FZBZk5GfAYpE9 MQCZMemsCTxhhqKnG0YOxjWNqausx+96v41UePG+k06gsuDtthq8yzgb7vl4SfevDIb9GBB9C9UM0 9yo0pLnQ==; Received: from [50.53.2.24] (helo=bombadil.infradead.org) by bombadil.infradead.org with esmtpsa (Exim 4.98 #2 (Red Hat Linux)) id 1tWV0l-00000000HSu-2rTk; Sat, 11 Jan 2025 06:30:19 +0000 From: Randy Dunlap To: linux-kernel@vger.kernel.org Cc: Randy Dunlap , Andrew Morton Subject: [PATCH] latencytop: use correct kernel-doc format for func params Date: Fri, 10 Jan 2025 22:30:19 -0800 Message-ID: <20250111063019.910730-1-rdunlap@infradead.org> X-Mailer: git-send-email 2.47.1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Use a ':' instead of a '-' after function parameters to eliminate kernel-doc warnings. kernel/latencytop.c:177: warning: Function parameter or struct member 'tsk'= not described in '__account_scheduler_latency' ../kernel/latencytop.c:177: warning: Function parameter or struct member 'u= secs' not described in '__account_scheduler_latency' ../kernel/latencytop.c:177: warning: Function parameter or struct member 'i= nter' not described in '__account_scheduler_latency' Fixes: ad0b0fd554df ("sched, latencytop: incorporate review feedback from A= ndrew Morton") Signed-off-by: Randy Dunlap Cc: Andrew Morton --- kernel/latencytop.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) --- linux-next-20250108.orig/kernel/latencytop.c +++ linux-next-20250108/kernel/latencytop.c @@ -158,9 +158,9 @@ account_global_scheduler_latency(struct =20 /** * __account_scheduler_latency - record an occurred latency - * @tsk - the task struct of the task hitting the latency - * @usecs - the duration of the latency in microseconds - * @inter - 1 if the sleep was interruptible, 0 if uninterruptible + * @tsk: the task struct of the task hitting the latency + * @usecs: the duration of the latency in microseconds + * @inter: 1 if the sleep was interruptible, 0 if uninterruptible * * This function is the main entry point for recording latency entries * as called by the scheduler.