From: Thomas Zimmermann <tzimmermann@suse.de>
To: Yang Yingliang <yangyingliang@huawei.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: airlied@linux.ie
Subject: Re: [PATCH -next] drm: correct function name drm_legacy_ctxbitmap_flush()
Date: Sun, 16 May 2021 22:09:43 +0200 [thread overview]
Message-ID: <b0ddf30e-d830-5827-e94b-bc0988f644d3@suse.de> (raw)
In-Reply-To: <20210513071918.1728535-1-yangyingliang@huawei.com>
[-- Attachment #1.1: Type: text/plain, Size: 1231 bytes --]
Hi
Am 13.05.21 um 09:19 schrieb Yang Yingliang:
> Fix the following make W=1 kernel build warning:
>
> drivers/gpu/drm/drm_context.c:136: warning: expecting prototype for drm_ctxbitmap_flush(). Prototype was for drm_legacy_ctxbitmap_flush() instead
>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Added to drm-misc-next. Thanks!
Best regards
Thomas
> ---
> drivers/gpu/drm/drm_context.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_context.c b/drivers/gpu/drm/drm_context.c
> index c99be950bf17..acbec1ddd583 100644
> --- a/drivers/gpu/drm/drm_context.c
> +++ b/drivers/gpu/drm/drm_context.c
> @@ -124,7 +124,7 @@ void drm_legacy_ctxbitmap_cleanup(struct drm_device
* dev)
> }
>
> /**
> - * drm_ctxbitmap_flush() - Flush all contexts owned by a file
> + * drm_legacy_ctxbitmap_flush() - Flush all contexts owned by a file
> * @dev: DRM device to operate on
> * @file: Open file to flush contexts for
> *
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2021-05-16 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 7:19 [PATCH -next] drm: correct function name drm_legacy_ctxbitmap_flush() Yang Yingliang
2021-05-16 20:09 ` Thomas Zimmermann [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=b0ddf30e-d830-5827-e94b-bc0988f644d3@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangyingliang@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).