dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Felix Kuehling <Felix.Kuehling@amd.com>
Cc: kbuild-all@lists.01.org, Kent Russell <kent.russell@amd.com>,
	dri-devel@lists.freedesktop.org
Subject: [RFC PATCH radeon-alex] drm/amdgpu: kfd_initialized can be static
Date: Wed, 23 Sep 2020 10:28:28 +0800	[thread overview]
Message-ID: <20200923022828.GA49981@6c0fda7302fc> (raw)
In-Reply-To: <202009231033.xsCmjah5%lkp@intel.com>


Fixes: 0b54e1e30e9f ("drm/amdgpu: Fix handling of KFD initialization failures")
Signed-off-by: kernel test robot <lkp@intel.com>
---
 amdgpu_amdkfd.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
index 7f14461f7f402..01780bb8727f6 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
@@ -36,7 +36,7 @@
  */
 uint64_t amdgpu_amdkfd_total_mem_size;
 
-bool kfd_initialized;
+static bool kfd_initialized;
 
 int amdgpu_amdkfd_init(void)
 {
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-09-23  2:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23  2:28 [radeon-alex:amd-staging-drm-next 443/482] drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:39:6: sparse: sparse: symbol 'kfd_initialized' was not declared. Should it be kernel test robot
2020-09-23  2:28 ` kernel test robot [this message]
2020-10-08 22:21   ` [RFC PATCH radeon-alex] drm/amdgpu: kfd_initialized can be static Felix Kuehling

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=20200923022828.GA49981@6c0fda7302fc \
    --to=lkp@intel.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kbuild-all@lists.01.org \
    --cc=kent.russell@amd.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