From nobody Sat May 10 03:03:29 2025 Delivered-To: importer2@patchew.org Received-SPF: pass (zohomail.com: domain of vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; envelope-from=linux-kernel-owner@vger.kernel.org; helo=vger.kernel.org; Authentication-Results: mx.zohomail.com; spf=pass (zohomail.com: domain of vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail(p=none dis=none) header.from=linux.alibaba.com ARC-Seal: i=1; a=rsa-sha256; t=1605257920; cv=none; d=zohomail.com; s=zohoarc; b=KqFd4wwB6vgaL1c31eLfBio0zeb15m6IqnIbK2blz5UkJF7GOV449lnT4DhLbImnGBacc8ZhEjrnmMaI5Pmys81ghjDaJywOqBiNJ/JYxohUN6fJvDv4q76H8ls8f8ZyNLnTlLCcOAr6M5cH0VT37tQEHMuORInYOr1bQ9jNxYY= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1605257920; h=Cc:Date:From:In-Reply-To:List-Id:Message-ID:References:Subject:To; bh=G/fAdUiCJo/qI4lEcz6FVTjQIJBVWfPMr6XFNxZgRx4=; b=QG7tuYv/SKNNfiK1ws2e5srRTR3K95AH35sJAHEK6GLrj8psFt5ecf2AYNRMAWd7/q1jT9yPGRl83JROwop6kIB/3eFrzYQjng8YpXUFNZJjAycCWFhjjBdFD0xosUBeJyinvsrp4HSN4gMbHjr/LhhERaPllaoRl9Obg73azk0= ARC-Authentication-Results: i=1; mx.zohomail.com; spf=pass (zohomail.com: domain of vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail header.from= (p=none dis=none) header.from= Return-Path: Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mx.zohomail.com with SMTP id 1605257920906124.64530046371874; Fri, 13 Nov 2020 00:58:40 -0800 (PST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726342AbgKMI6j (ORCPT ); Fri, 13 Nov 2020 03:58:39 -0500 Received: from out30-43.freemail.mail.aliyun.com ([115.124.30.43]:39734 "EHLO out30-43.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726149AbgKMI6h (ORCPT ); Fri, 13 Nov 2020 03:58:37 -0500 Received: from aliy80.localdomain(mailfrom:alex.shi@linux.alibaba.com fp:SMTPD_---0UFAepvk_1605257910) by smtp.aliyun-inc.com(127.0.0.1); Fri, 13 Nov 2020 16:58:35 +0800 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R511e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e04357;MF=alex.shi@linux.alibaba.com;NM=1;PH=DS;RN=4;SR=0;TI=SMTPD_---0UFAepvk_1605257910; From: Alex Shi Cc: Peter Zijlstra , Ingo Molnar , Will Deacon , linux-kernel@vger.kernel.org Subject: [PATCH] locking/rtmutex: add missed kernel-doc markup Date: Fri, 13 Nov 2020 16:58:11 +0800 Message-Id: <1605257895-5536-2-git-send-email-alex.shi@linux.alibaba.com> X-Mailer: git-send-email 1.8.3.1 In-Reply-To: <1605257895-5536-1-git-send-email-alex.shi@linux.alibaba.com> References: <1605257895-5536-1-git-send-email-alex.shi@linux.alibaba.com> To: unlisted-recipients:; (no To-header on input) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" To fix the following issues: kernel/locking/rtmutex.c:1612: warning: Function parameter or member 'lock' not described in '__rt_mutex_futex_unlock' kernel/locking/rtmutex.c:1612: warning: Function parameter or member 'wake_q' not described in '__rt_mutex_futex_unlock' kernel/locking/rtmutex.c:1675: warning: Function parameter or member 'name' not described in '__rt_mutex_init' kernel/locking/rtmutex.c:1675: warning: Function parameter or member 'key' not described in '__rt_mutex_init' Signed-off-by: Alex Shi Cc: Peter Zijlstra =20 Cc: Ingo Molnar =20 Cc: Will Deacon =20 Cc: linux-kernel@vger.kernel.org=20 --- kernel/locking/rtmutex.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c index cfdd5b93264d..50fa521fe767 100644 --- a/kernel/locking/rtmutex.c +++ b/kernel/locking/rtmutex.c @@ -1604,8 +1604,11 @@ void __sched rt_mutex_unlock(struct rt_mutex *lock) EXPORT_SYMBOL_GPL(rt_mutex_unlock); =20 /** - * Futex variant, that since futex variants do not use the fast-path, can = be - * simple and will not need to retry. + * __rt_mutex_futex_unlock - Futex variant, that since futex variants + * do not use the fast-path, can be simple and will not need to retry. + * + * @lock: the rt_mutex to be unlocked + * @wake_q: wake queue head from which get the next lock waiter */ bool __sched __rt_mutex_futex_unlock(struct rt_mutex *lock, struct wake_q_head *wake_q) @@ -1665,6 +1668,8 @@ EXPORT_SYMBOL_GPL(rt_mutex_destroy); * __rt_mutex_init - initialize the rt lock * * @lock: the rt lock to be initialized + * @name: the lock name used for debug + * @key: the lock class key used for debug * * Initialize the rt lock to unlocked state. * --=20 2.29.GIT