Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Luca Coelho <luciano.coelho@intel.com>, intel-gfx@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [Intel-gfx] [PATCH 3/4] drm/i915/tc: move legacy code out of the main _max_lane_count() func
Date: Wed, 19 Jul 2023 23:05:33 +0800	[thread overview]
Message-ID: <202307192225.QnmiapXD-lkp@intel.com> (raw)
In-Reply-To: <20230719132822.305612-4-luciano.coelho@intel.com>

Hi Luca,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-tip/drm-tip]

url:    https://github.com/intel-lab-lkp/linux/commits/Luca-Coelho/drm-i915-tc-rename-mtl_tc_port_get_pin_assignment_mask/20230719-213204
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:    https://lore.kernel.org/r/20230719132822.305612-4-luciano.coelho%40intel.com
patch subject: [Intel-gfx] [PATCH 3/4] drm/i915/tc: move legacy code out of the main _max_lane_count() func
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20230719/202307192225.QnmiapXD-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230719/202307192225.QnmiapXD-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202307192225.QnmiapXD-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/gpu/drm/i915/display/intel_tc.c: In function 'intel_tc_port_fia_max_lane_count':
>> drivers/gpu/drm/i915/display/intel_tc.c:354:21: error: 'struct intel_digital_port' has no member named 'tc_mode'
     354 |         if (dig_port->tc_mode != TC_PORT_DP_ALT)
         |                     ^~


vim +354 drivers/gpu/drm/i915/display/intel_tc.c

   349	
   350	int intel_tc_port_fia_max_lane_count(struct intel_digital_port *dig_port)
   351	{
   352		struct drm_i915_private *i915 = to_i915(dig_port->base.base.dev);
   353	
 > 354		if (dig_port->tc_mode != TC_PORT_DP_ALT)
   355			return 4;
   356	
   357		if (DISPLAY_VER(i915) >= 14)
   358			return mtl_tc_port_get_max_lane_count(dig_port);
   359	
   360		return intel_tc_port_get_max_lane_count(dig_port);
   361	}
   362	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2023-07-19 15:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 13:28 [Intel-gfx] [PATCH 0/4] drm/i915/tc: some clean-ups in max lane count handling code Luca Coelho
2023-07-19 13:28 ` [Intel-gfx] [PATCH 1/4] drm/i915/tc: rename mtl_tc_port_get_pin_assignment_mask() Luca Coelho
2023-07-19 13:28 ` [Intel-gfx] [PATCH 2/4] drm/i915/tc: make intel_tc_port_get_lane_mask() static Luca Coelho
2023-07-19 13:28 ` [Intel-gfx] [PATCH 3/4] drm/i915/tc: move legacy code out of the main _max_lane_count() func Luca Coelho
2023-07-19 15:05   ` kernel test robot [this message]
2023-07-19 13:28 ` [Intel-gfx] [PATCH 4/4] drm/i915/tc: remove "fia" from intel_tc_port_fia_max_lane_count() Luca Coelho
2023-07-19 15:48   ` kernel test robot
2023-07-19 16:28 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/tc: some clean-ups in max lane count handling code Patchwork

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=202307192225.QnmiapXD-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=luciano.coelho@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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