From nobody Mon Oct 6 21:02:47 2025 Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [160.30.148.34]) (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 5BA881D5AB7; Thu, 17 Jul 2025 02:42:10 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=160.30.148.34 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1752720135; cv=none; b=teKEXOBOsCwVJI2G9d7QPA1Q/wGC4lFnuu+5fKu4uu3qv9SYitwJvuE7UmSZFe9Sz9yFBoYNUK9CK/+RdelEaaTzvmc3wmwe2wdxCPhGqNS53O3Zo7SLnx4OrDWZfm9GcSY8U3K6oEB2ObVpwi2qNlIeNOjx+UqJ0kU1Ky04DUQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1752720135; c=relaxed/simple; bh=s+t/uu9h2gvGqffSfaH4EUk1H5BqMIGobLIMcwtt6Oo=; h=Date:Message-ID:Mime-Version:From:To:Cc:Subject:Content-Type; b=pFNQtUXxyExQq+kn741rnKp1qd310bPyp8de1WJuxHKDND0D/BzGGvgk3JNGr8v6hQbTi+hQlkW5oS0Q2Ax0RYhCbaGcWfRU3gMQC0qfeGrs6UyxZX9PHTpt/W96mPO7SJfjwBNPsQaDQ7THgeX3THJ0UY5+4jCjqgIEDf5Vi+c= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zte.com.cn; spf=pass smtp.mailfrom=zte.com.cn; arc=none smtp.client-ip=160.30.148.34 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zte.com.cn Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=zte.com.cn Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4bjHJJ75ljz6Fy5m; Thu, 17 Jul 2025 10:42:08 +0800 (CST) Received: from xaxapp01.zte.com.cn ([10.88.99.176]) by mse-fl1.zte.com.cn with SMTP id 56H2fwwc004125; Thu, 17 Jul 2025 10:41:58 +0800 (+08) (envelope-from jiang.peng9@zte.com.cn) Received: from mapi (xaxapp01[null]) by mapi (Zmail) with MAPI id mid31; Thu, 17 Jul 2025 10:41:59 +0800 (CST) Date: Thu, 17 Jul 2025 10:41:59 +0800 (CST) X-Zmail-TransId: 2af9687862f7ffffffffa49-5bc46 X-Mailer: Zmail v1.0 Message-ID: <202507171041593886W7pGra5n2hPMaT1j17NV@zte.com.cn> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 From: To: Cc: , , , , , , , , , , Subject: =?UTF-8?B?W1BBVENIIHYzXSB2aXJ0aW86IFVwZGF0ZSBrZXJuZWxkb2MgaW4gZHJpdmVycy92aXJ0aW8vdmlydGlvX2RtYV9idWYuYw==?= X-MAIL: mse-fl1.zte.com.cn 56H2fwwc004125 X-TLS: YES X-SPF-DOMAIN: zte.com.cn X-ENVELOPE-SENDER: jiang.peng9@zte.com.cn X-SPF: None X-SOURCE-IP: 10.5.228.132 unknown Thu, 17 Jul 2025 10:42:09 +0800 X-Fangmail-Anti-Spam-Filtered: true X-Fangmail-MID-QID: 68786300.000/4bjHJJ75ljz6Fy5m Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" From: Peng Jiang Fix kernel-doc descriptions in virtio_dma_buf.c to fix W=3D1 warnings: drivers/virtio/virtio_dma_buf.c:41 function parameter 'dma_buf' not describ= ed in 'virtio_dma_buf_attach' drivers/virtio/virtio_dma_buf.c:41 function parameter 'attach' not describe= d in 'virtio_dma_buf_attach' Signed-off-by: Peng Jiang --- drivers/virtio/virtio_dma_buf.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/drivers/virtio/virtio_dma_buf.c b/drivers/virtio/virtio_dma_bu= f.c index 3fe1d03b0645..986cc73c503f 100644 --- a/drivers/virtio/virtio_dma_buf.c +++ b/drivers/virtio/virtio_dma_buf.c @@ -16,6 +16,8 @@ * This wraps dma_buf_export() to allow virtio drivers to create a dma-buf * for an virtio exported object that can be queried by other virtio drive= rs * for the object's UUID. + * + * Returns: dma-buf pointer on success, ERR_PTR on failure. */ struct dma_buf *virtio_dma_buf_export (const struct dma_buf_export_info *exp_info) @@ -36,6 +38,14 @@ EXPORT_SYMBOL(virtio_dma_buf_export); /** * virtio_dma_buf_attach - mandatory attach callback for virtio dma-bufs + * @dma_buf: DMA buffer being attached to a device + * @attach: Attachment metadata for the device-dma_buf association + * + * Allows virtio devices to perform device-specific setup when a DMA buffer + * is attached to a device. This is part of the DMA-BUF sharing mechanism + * that enables virtio devices to interoperate with other subsystems. + * + * Returns: 0 on success, negative on failure. */ int virtio_dma_buf_attach(struct dma_buf *dma_buf, struct dma_buf_attachment *attach) --=20 2.25.1