From: Sumit Semwal <sumit.semwal@linaro.org>
To: Christian König <christian.koenig@amd.com>
Cc: leon@kernel.org, broonie@kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: [PATCH] dma-buf: fix htmldocs error for dma_buf_attach_revocable
Date: Fri, 10 Apr 2026 19:36:59 +0530 [thread overview]
Message-ID: <CAO_48GHyBz-CEap=icQDKqVsBgCy+DNazd6ANzf0NucE5yc1cg@mail.gmail.com> (raw)
In-Reply-To: <c427afeb-15eb-4a46-aa6c-fe24631d24ae@amd.com>
Hi Christian,
On Fri, 10 Apr 2026 at 18:14, Christian König <christian.koenig@amd.com> wrote:
>
> On 4/10/26 14:37, Sumit Semwal wrote:
> > linux-next testing showed this htmldoc error due to a missing extra
> > line in the comments; add it.
> >
> > Fixes: be6d4c9e9d714 ("dma-buf: Add dma_buf_attach_revocable()")
> > Reported-by: Mark Brown <broonie@kernel.org>
> > Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
>
> Reviewed-by: Christian König <christian.koenig@amd.com>
Thank you; pushed to drm-misc-next-fixes!
Best,
Sumit
>
> > ---
> > drivers/dma-buf/dma-buf.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
> > index a202a308c079..532c3f14bf9d 100644
> > --- a/drivers/dma-buf/dma-buf.c
> > +++ b/drivers/dma-buf/dma-buf.c
> > @@ -1353,6 +1353,7 @@ EXPORT_SYMBOL_NS_GPL(dma_buf_attach_revocable, "DMA_BUF");
> > * Upon return importers may continue to access the DMA-buf memory. The caller
> > * must do two additional waits to ensure that the memory is no longer being
> > * accessed:
> > + *
> > * 1) Until dma_resv_wait_timeout() retires fences the importer is allowed to
> > * fully access the memory.
> > * 2) Until the importer calls unmap it is allowed to speculatively
>
next prev parent reply other threads:[~2026-04-10 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 12:37 [PATCH] dma-buf: fix htmldocs error for dma_buf_attach_revocable Sumit Semwal
2026-04-10 12:43 ` Christian König
2026-04-10 14:06 ` Sumit Semwal [this message]
2026-04-11 23:39 ` Claude review: " Claude Code Review Bot
2026-04-11 23:39 ` Claude Code Review Bot
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='CAO_48GHyBz-CEap=icQDKqVsBgCy+DNazd6ANzf0NucE5yc1cg@mail.gmail.com' \
--to=sumit.semwal@linaro.org \
--cc=broonie@kernel.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.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