From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm: Fix up kerneldoc for new drm_gem_dmabuf_export()
Date: Thu, 6 Oct 2016 11:20:14 +0200 [thread overview]
Message-ID: <20161006092014.GQ20761@phenom.ffwll.local> (raw)
In-Reply-To: <20161005174056.29869-1-chris@chris-wilson.co.uk>
On Wed, Oct 05, 2016 at 06:40:56PM +0100, Chris Wilson wrote:
> I hit send before completing a make htmldoc, and lo I forgot to fix up
> the cut'n'paste.
>
> Fixes: a4fce9cb782a ("drm/prime: Take a ref on the drm_dev when exporting...")
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: stable@vger.kernel.org
Thanks for the quick fix, applied to drm-misc.
-Daniel
> ---
> drivers/gpu/drm/drm_prime.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c
> index 875df8d719fb..b22a94dd7b53 100644
> --- a/drivers/gpu/drm/drm_prime.c
> +++ b/drivers/gpu/drm/drm_prime.c
> @@ -285,7 +285,8 @@ static void drm_gem_unmap_dma_buf(struct dma_buf_attachment *attach,
>
> /**
> * drm_gem_dmabuf_export - dma_buf export implementation for GEM
> - * @dma_buf: buffer to be exported
> + * @dev: parent device for the exported dmabuf
> + * @exp_info: the export information used by dma_buf_export()
> *
> * This wraps dma_buf_export() for use by generic GEM drivers that are using
> * drm_gem_dmabuf_release(). In addition to calling dma_buf_export(), we take
> --
> 2.9.3
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2016-10-06 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 17:40 [PATCH] drm: Fix up kerneldoc for new drm_gem_dmabuf_export() Chris Wilson
2016-10-06 9:20 ` Daniel Vetter [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=20161006092014.GQ20761@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=stable@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