dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dave Airlie <airlied@redhat.com>
Cc: kbuild-all@lists.01.org, dri-devel@lists.freedesktop.org
Subject: [RFC PATCH airlied] drm/i915/display: pipe_config_mismatch can be static
Date: Thu, 14 Oct 2021 04:20:01 +0800	[thread overview]
Message-ID: <20211013202001.GA63140@759f3dc4db3c> (raw)
In-Reply-To: <202110140403.Vbr7MqCf-lkp@intel.com>

drivers/gpu/drm/i915/display/intel_dump_verify.c:19:1: warning: symbol 'pipe_config_mismatch' was not declared. Should it be static?

Fixes: 678661f2ff1b ("drm/i915/display: move display dump/verify code to a separate file")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
 intel_dump_verify.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/display/intel_dump_verify.c b/drivers/gpu/drm/i915/display/intel_dump_verify.c
index dab85805a569d..ad4448f7b0291 100644
--- a/drivers/gpu/drm/i915/display/intel_dump_verify.c
+++ b/drivers/gpu/drm/i915/display/intel_dump_verify.c
@@ -15,7 +15,7 @@
 #include "intel_snps_phy.h"
 #include "intel_vrr.h"
 
-void __printf(4, 5)
+static void __printf(4, 5)
 pipe_config_mismatch(bool fastset, const struct intel_crtc *crtc,
 		     const char *name, const char *format, ...)
 {

      reply	other threads:[~2021-10-13 20:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13 20:19 [airlied:drm-intel-display-refactor 12/19] drivers/gpu/drm/i915/display/intel_dump_verify.c:19:1: sparse: sparse: symbol 'pipe_config_mismatch' was not declared. Should it be static? kernel test robot
2021-10-13 20:20 ` kernel test robot [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=20211013202001.GA63140@759f3dc4db3c \
    --to=lkp@intel.com \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kbuild-all@lists.01.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