From: Daniel Vetter <daniel@ffwll.ch>
To: "Maíra Canal" <mcanal@igalia.com>
Cc: "André Almeida" <andrealmeid@igalia.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
intel-gfx@lists.freedesktop.org,
"Simon Ser" <contact@emersion.fr>,
dri-devel@lists.freedesktop.org,
"Maxime Ripard" <mripard@kernel.org>,
"Melissa Wen" <mwen@igalia.com>,
"VMware Graphics Reviewers"
<linux-graphics-maintainer@vmware.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Christian König" <christian.koenig@amd.com>,
"Zack Rusin" <zackr@vmware.com>
Subject: Re: [Intel-gfx] [PATCH 5/5] drm/plane: Unexport drm_any_plane_has_format()
Date: Wed, 11 Jan 2023 23:50:15 +0100 [thread overview]
Message-ID: <Y789J/xm++6lfad7@phenom.ffwll.local> (raw)
In-Reply-To: <20230109105807.18172-6-mcanal@igalia.com>
On Mon, Jan 09, 2023 at 07:58:08AM -0300, Maíra Canal wrote:
> As the format validation is being dealt with exclusively
> inside framebuffer_check(), there is no need to export the
> drm_any_plane_has_format() symbol.
>
> Therefore, unexport the drm_any_plane_has_format() symbol, reinforcing
> that format validation is being dealt with by the DRM API.
>
> Signed-off-by: Maíra Canal <mcanal@igalia.com>
Usually we also delete the kerneldoc at that point, since that's mainly
for driver authors and they don't need this anymore. With that
Also please move the function decl to the drm_crtc_internal.h since this
is no longer used outside of drm core/helper code.
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
> drivers/gpu/drm/drm_plane.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_plane.c b/drivers/gpu/drm/drm_plane.c
> index 24e7998d1731..67c0ab60c7b6 100644
> --- a/drivers/gpu/drm/drm_plane.c
> +++ b/drivers/gpu/drm/drm_plane.c
> @@ -837,7 +837,6 @@ bool drm_any_plane_has_format(struct drm_device *dev,
>
> return false;
> }
> -EXPORT_SYMBOL(drm_any_plane_has_format);
>
> /*
> * __setplane_internal - setplane handler for internal callers
> --
> 2.39.0
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2023-01-11 22:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 10:58 [Intel-gfx] [PATCH 0/5] Check for valid framebuffer's format Maíra Canal
2023-01-09 10:58 ` [Intel-gfx] [PATCH 1/5] drm/framebuffer: Check for valid formats Maíra Canal
2023-01-11 22:48 ` Daniel Vetter
2023-01-09 10:58 ` [Intel-gfx] [PATCH 2/5] drm/amdgpu: Remove redundant framebuffer format check Maíra Canal
2023-01-12 12:17 ` Simon Ser
2023-01-09 10:58 ` [Intel-gfx] [PATCH 3/5] drm/i915: " Maíra Canal
2023-01-12 12:18 ` Simon Ser
2023-01-12 12:43 ` Ville Syrjälä
2023-01-12 14:07 ` Maíra Canal
2023-01-12 15:15 ` Ville Syrjälä
2023-01-09 10:58 ` [Intel-gfx] [PATCH 4/5] drm/vmwgfx: " Maíra Canal
2023-01-12 2:52 ` Zack Rusin
2023-01-09 10:58 ` [Intel-gfx] [PATCH 5/5] drm/plane: Unexport drm_any_plane_has_format() Maíra Canal
2023-01-11 22:50 ` 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=Y789J/xm++6lfad7@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=andrealmeid@igalia.com \
--cc=christian.koenig@amd.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=mcanal@igalia.com \
--cc=mripard@kernel.org \
--cc=mwen@igalia.com \
--cc=rodrigo.vivi@intel.com \
--cc=tzimmermann@suse.de \
--cc=zackr@vmware.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