linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Guo, Bing" <Bing.Guo@amd.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Alex Deucher <alexander.deucher@amd.com>,
	Wenjing Liu <Wenjing.Liu@amd.com>
Subject: [linux-next:master 2923/3376] drivers/gpu/drm/amd/amdgpu/../display/dc/dsc/rc_calc_dpi.c:116: undefined reference to `__udivdi3'
Date: Wed, 24 Nov 2021 18:16:22 +0800	[thread overview]
Message-ID: <202111241842.pSYgc67V-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   4b74e088fef6ce8cc513f935ce236c38bdf5f67b
commit: c34f1652a18c4bd4d0bb9e7c7d946861c3ed73c9 [2923/3376] drm/amd/display: fixed an error related to 4:2:0/4:2:2 DSC
config: i386-randconfig-a014-20211122 (https://download.01.org/0day-ci/archive/20211124/202111241842.pSYgc67V-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=c34f1652a18c4bd4d0bb9e7c7d946861c3ed73c9
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout c34f1652a18c4bd4d0bb9e7c7d946861c3ed73c9
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   ld: drivers/gpu/drm/amd/display/dc/dsc/rc_calc_dpi.o: in function `dscc_compute_dsc_parameters':
>> drivers/gpu/drm/amd/amdgpu/../display/dc/dsc/rc_calc_dpi.c:116: undefined reference to `__udivdi3'


vim +116 drivers/gpu/drm/amd/amdgpu/../display/dc/dsc/rc_calc_dpi.c

    97	
    98	int dscc_compute_dsc_parameters(const struct drm_dsc_config *pps, struct dsc_parameters *dsc_params)
    99	{
   100		int              ret;
   101		struct rc_params rc;
   102		struct drm_dsc_config   dsc_cfg;
   103	
   104		calc_rc_params(&rc, pps);
   105		dsc_params->pps = *pps;
   106		dsc_params->pps.initial_scale_value = 8 * rc.rc_model_size / (rc.rc_model_size - rc.initial_fullness_offset);
   107	
   108		copy_pps_fields(&dsc_cfg, &dsc_params->pps);
   109		copy_rc_to_cfg(&dsc_cfg, &rc);
   110	
   111		dsc_cfg.mux_word_size = dsc_params->pps.bits_per_component <= 10 ? 48 : 64;
   112	
   113		ret = drm_dsc_compute_rc_parameters(&dsc_cfg);
   114		dsc_params->bytes_per_pixel =
   115				(uint32_t)(((unsigned long long)dsc_cfg.slice_chunk_size * 0x10000000 + (dsc_cfg.slice_width - 1))
 > 116								/ (uint32_t)dsc_cfg.slice_width);  //ROUND-UP
   117	
   118		copy_pps_fields(&dsc_params->pps, &dsc_cfg);
   119		dsc_params->rc_buffer_model_size = dsc_cfg.rc_bits;
   120		return ret;
   121	}
   122	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org


                 reply	other threads:[~2021-11-24 10:17 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=202111241842.pSYgc67V-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Bing.Guo@amd.com \
    --cc=Wenjing.Liu@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.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