From: kernel test robot <lkp@intel.com>
To: Jack Xiao <Jack.Xiao@amd.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Alex Deucher <alexander.deucher@amd.com>,
Hawking Zhang <Hawking.Zhang@amd.com>
Subject: [agd5f:drm-next 395/460] drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c:864:13: warning: variable 'r' set but not used
Date: Thu, 5 May 2022 03:39:38 +0800 [thread overview]
Message-ID: <202205050315.yMErlGvA-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/agd5f/linux.git drm-next
head: d6ffefccf7f04eefddc8e8aa35fb4afe05a42e0c
commit: e3652b0976f383dea912607a404e974632b019b1 [395/460] drm/amdgpu/mes: add helper functions to alloc/free ctx metadata
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20220505/202205050315.yMErlGvA-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git remote add agd5f https://gitlab.freedesktop.org/agd5f/linux.git
git fetch --no-tags agd5f drm-next
git checkout e3652b0976f383dea912607a404e974632b019b1
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=alpha SHELL=/bin/bash drivers/gpu/drm/amd/amdgpu/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c: In function 'amdgpu_mes_ctx_alloc_meta_data':
>> drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c:864:13: warning: variable 'r' set but not used [-Wunused-but-set-variable]
864 | int r;
| ^
vim +/r +864 drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c
860
861 int amdgpu_mes_ctx_alloc_meta_data(struct amdgpu_device *adev,
862 struct amdgpu_mes_ctx_data *ctx_data)
863 {
> 864 int r;
865
866 r = amdgpu_bo_create_kernel(adev,
867 sizeof(struct amdgpu_mes_ctx_meta_data),
868 PAGE_SIZE, AMDGPU_GEM_DOMAIN_GTT,
869 &ctx_data->meta_data_obj, NULL,
870 &ctx_data->meta_data_ptr);
871 if (!ctx_data->meta_data_obj)
872 return -ENOMEM;
873
874 memset(ctx_data->meta_data_ptr, 0,
875 sizeof(struct amdgpu_mes_ctx_meta_data));
876
877 return 0;
878 }
879
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-04 19:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202205050315.yMErlGvA-lkp@intel.com \
--to=lkp@intel.com \
--cc=Hawking.Zhang@amd.com \
--cc=Jack.Xiao@amd.com \
--cc=alexander.deucher@amd.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®