From: "Christian König" <christian.koenig@amd.com>
To: "Nicolás Antinori" <nico.antinori.7@gmail.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH] dma-buf: docs: remove invalid struct member
Date: Fri, 3 Jul 2026 09:18:19 +0200 [thread overview]
Message-ID: <c637c757-181b-494b-9866-27539b0fa474@amd.com> (raw)
In-Reply-To: <20260702171234.31030-1-nico.antinori.7@gmail.com>
On 7/2/26 19:12, Nicolás Antinori wrote:
> In the structs dma_fence_array and dma_fence_chain, the field 'lock'
> has been removed, but its documentation comment remained. Remove the
> stale descriptions to clear up the following kernel-doc warnings:
>
> WARNING: ./include/linux/dma-fence-array.h:47 Excess struct member 'lock' description in 'dma_fence_array'
> WARNING: ./include/linux/dma-fence-array.h:47 Excess struct member 'lock' description in 'dma_fence_array'
> WARNING: ./include/linux/dma-fence-chain.h:48 Excess struct member 'lock' description in 'dma_fence_chain'
> WARNING: ./include/linux/dma-fence-chain.h:48 Excess struct member 'lock' description in 'dma_fence_chain'
>
> Fixes: 5943243914b9 ("dma-buf: use inline lock for the dma-fence-array")
> Fixes: a408c0ca0c41 ("dma-buf: use inline lock for the dma-fence-chain")
> Signed-off-by: Nicolás Antinori <nico.antinori.7@gmail.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Going to push that to drm-misc-next later today.
Regards,
Christian.
> ---
> include/linux/dma-fence-array.h | 1 -
> include/linux/dma-fence-chain.h | 1 -
> 2 files changed, 2 deletions(-)
>
> diff --git a/include/linux/dma-fence-array.h b/include/linux/dma-fence-array.h
> index 1b1d87579c38..0c49d7ccefb6 100644
> --- a/include/linux/dma-fence-array.h
> +++ b/include/linux/dma-fence-array.h
> @@ -28,7 +28,6 @@ struct dma_fence_array_cb {
> /**
> * struct dma_fence_array - fence to represent an array of fences
> * @base: fence base class
> - * @lock: spinlock for fence handling
> * @num_fences: number of fences in the array
> * @num_pending: fences in the array still pending
> * @fences: array of the fences
> diff --git a/include/linux/dma-fence-chain.h b/include/linux/dma-fence-chain.h
> index df3beadf1515..42289f505164 100644
> --- a/include/linux/dma-fence-chain.h
> +++ b/include/linux/dma-fence-chain.h
> @@ -20,7 +20,6 @@
> * @prev: previous fence of the chain
> * @prev_seqno: original previous seqno before garbage collection
> * @fence: encapsulated fence
> - * @lock: spinlock for fence handling
> */
> struct dma_fence_chain {
> struct dma_fence base;
> --
> 2.47.3
>
prev parent reply other threads:[~2026-07-03 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 17:12 Nicolás Antinori
2026-07-03 7:18 ` Christian König [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c637c757-181b-494b-9866-27539b0fa474@amd.com \
--to=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=nico.antinori.7@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=sumit.semwal@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome