From: Daniel Vetter <daniel@ffwll.ch>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/hdcp: drm_hdcp_request_srm() as static
Date: Mon, 13 May 2019 22:06:16 +0200 [thread overview]
Message-ID: <20190513200616.GX17751@phenom.ffwll.local> (raw)
In-Reply-To: <20190513133504.18612-1-ramalingam.c@intel.com>
On Mon, May 13, 2019 at 07:05:04PM +0530, Ramalingam C wrote:
> Below Sparsh warnings are fixed.
>
> Commit: drm: revocation check at drm subsystem
> +drivers/gpu/drm/drm_hdcp.c:235:6: warning: symbol
> 'drm_hdcp_request_srm' was not declared. Should it be static?
> +drivers/gpu/drm/drm_hdcp.c:27:3: warning: symbol 'srm_data' was not
> declared. Should it be static?
> +drivers/gpu/drm/drm_hdcp.c:317:5: warning: symbol 'drm_setup_hdcp_srm'
> was not declared. Should it be static?
> +drivers/gpu/drm/drm_hdcp.c:327:6: warning: symbol
> 'drm_teardown_hdcp_srm' was not declared. Should it be static?
>
> cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Reported-by: kbuild test robot <lkp@intel.com>
> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
Merged with Dave's irc ack into drm-intel-next-queued, thanks for your
quick fix.
-Daniel
> ---
> drivers/gpu/drm/drm_hdcp.c | 6 ++++--
> drivers/gpu/drm/drm_internal.h | 1 +
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_hdcp.c b/drivers/gpu/drm/drm_hdcp.c
> index 0da7b3718bad..cd837bd409f7 100644
> --- a/drivers/gpu/drm/drm_hdcp.c
> +++ b/drivers/gpu/drm/drm_hdcp.c
> @@ -21,7 +21,9 @@
> #include <drm/drm_mode_object.h>
> #include <drm/drm_connector.h>
>
> -struct hdcp_srm {
> +#include "drm_internal.h"
> +
> +static struct hdcp_srm {
> u32 revoked_ksv_cnt;
> u8 *revoked_ksv_list;
>
> @@ -235,7 +237,7 @@ static void drm_hdcp_srm_update(const u8 *buf, size_t count)
> drm_hdcp_parse_hdcp2_srm(buf, count);
> }
>
> -void drm_hdcp_request_srm(struct drm_device *drm_dev)
> +static void drm_hdcp_request_srm(struct drm_device *drm_dev)
> {
> char fw_name[36] = "display_hdcp_srm.bin";
> const struct firmware *fw;
> diff --git a/drivers/gpu/drm/drm_internal.h b/drivers/gpu/drm/drm_internal.h
> index 476a422414f6..65abf3a69b40 100644
> --- a/drivers/gpu/drm/drm_internal.h
> +++ b/drivers/gpu/drm/drm_internal.h
> @@ -106,6 +106,7 @@ void drm_sysfs_connector_remove(struct drm_connector *connector);
> void drm_sysfs_lease_event(struct drm_device *dev);
>
> /* drm_gem.c */
> +struct drm_gem_object;
> int drm_gem_init(struct drm_device *dev);
> void drm_gem_destroy(struct drm_device *dev);
> int drm_gem_handle_create_tail(struct drm_file *file_priv,
> --
> 2.19.1
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-05-13 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 13:35 [PATCH] drm/hdcp: drm_hdcp_request_srm() as static Ramalingam C
2019-05-13 14:51 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2019-05-13 15:41 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-13 19:26 ` ✓ Fi.CI.IGT: " Patchwork
2019-05-13 20:06 ` 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=20190513200616.GX17751@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ramalingam.c@intel.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