Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	intel-xe@lists.freedesktop.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	intel-gfx@lists.freedesktop.org,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH v3 10/12] drm/xe: Make xe_ggtt_pt_ops private
Date: Fri, 4 Oct 2024 21:30:05 +0800	[thread overview]
Message-ID: <202410042102.EdHRO7JI-lkp@intel.com> (raw)
In-Reply-To: <20241003154421.33805-11-maarten.lankhorst@linux.intel.com>

Hi Maarten,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on linus/master v6.12-rc1]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip next-20241004]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Maarten-Lankhorst/drm-xe-display-Handle-stolen-bar-readout-in-the-same-way-as-lmem/20241004-000534
base:   https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link:    https://lore.kernel.org/r/20241003154421.33805-11-maarten.lankhorst%40linux.intel.com
patch subject: [PATCH v3 10/12] drm/xe: Make xe_ggtt_pt_ops private
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20241004/202410042102.EdHRO7JI-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241004/202410042102.EdHRO7JI-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/202410042102.EdHRO7JI-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/xe/xe_ggtt.c:906: warning: expecting prototype for xe_ggtt_write_pte(). Prototype was for xe_ggtt_get_encode_pte_bo_fn() instead


vim +906 drivers/gpu/drm/xe/xe_ggtt.c

   897	
   898	/**
   899	 * xe_ggtt_write_pte - Write a PTE to the GGTT
   900	 * @ggtt: &xe_ggtt
   901	 * @offset: the offset for which the mapping should be written.
   902	 *
   903	 * Used by display for DPT and GGTT paths to enccode BO's.
   904	 */
   905	xe_ggtt_pte_encode_bo_fn xe_ggtt_get_encode_pte_bo_fn(struct xe_ggtt *ggtt)
 > 906	{

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

  parent reply	other threads:[~2024-10-04 13:31 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03 15:44 [PATCH v3 00/12] drm/xe: Reduce flickering when inheriting BIOS fb Maarten Lankhorst
2024-10-03 15:44 ` [PATCH v3 01/12] drm/xe/display: Handle stolen bar readout in the same way as lmem Maarten Lankhorst
2024-10-07 18:52   ` Lucas De Marchi
2024-10-03 15:44 ` [PATCH v3 02/12] drm/xe: Remove double pageflip Maarten Lankhorst
2024-10-11  9:38   ` Govindapillai, Vinod
2024-10-03 15:44 ` [PATCH v3 03/12] drm/i915/display: Use async flip when available for initial plane config Maarten Lankhorst
2024-10-03 15:58   ` Jani Nikula
2024-10-03 20:51     ` Maarten Lankhorst
2024-10-03 16:14   ` Ville Syrjälä
2024-10-03 20:50     ` Maarten Lankhorst
2024-10-03 20:59       ` Ville Syrjälä
2024-10-04 12:48   ` kernel test robot
2024-10-07 10:23   ` [PATCH v2.1 " Maarten Lankhorst
2024-10-03 15:44 ` [PATCH v3 04/12] drm/xe/display: Remove single wait for vblank Maarten Lankhorst
2024-10-03 15:44 ` [PATCH v3 05/12] drm/xe: Move suballocator init to after display init Maarten Lankhorst
2024-10-03 15:44 ` [PATCH v3 06/12] drm/xe: Use xe_ggtt_map_bo_unlocked for resume Maarten Lankhorst
2024-10-04  6:27   ` Matthew Brost
2024-10-03 15:44 ` [PATCH v3 07/12] drm/xe: Add xe_ggtt_might_lock Maarten Lankhorst
2024-10-04  6:28   ` Matthew Brost
2024-10-03 15:44 ` [PATCH v3 08/12] drm/xe: Add xe_ggtt_alloc Maarten Lankhorst
2024-10-04  6:33   ` Matthew Brost
2024-10-03 15:44 ` [PATCH v3 09/12] drm/xe: Abstract read/write functions for GGTT PTEs Maarten Lankhorst
2024-10-04  6:35   ` Matthew Brost
2024-10-03 15:44 ` [PATCH v3 10/12] drm/xe: Make xe_ggtt_pt_ops private Maarten Lankhorst
2024-10-04  6:38   ` Matthew Brost
2024-10-04 13:30   ` kernel test robot [this message]
2024-10-07 18:40   ` Lucas De Marchi
2024-10-03 15:44 ` [PATCH v3 11/12] drm/xe/display: Stop dereferencing ggtt in xe_fb_pin Maarten Lankhorst
2024-10-07 16:58   ` Matthew Brost
2024-10-03 15:44 ` [PATCH v3 12/12] drm/xe: Move struct xe_ggtt to xe_ggtt.c Maarten Lankhorst
2024-10-04  6:41   ` Matthew Brost
2024-10-03 19:53 ` ✗ Fi.CI.BUILD: failure for drm/xe: Reduce flickering when inheriting BIOS fb Patchwork
2024-10-08  3:16 ` ✗ Fi.CI.BUILD: failure for drm/xe: Reduce flickering when inheriting BIOS fb. (rev2) 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=202410042102.EdHRO7JI-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=llvm@lists.linux.dev \
    --cc=maarten.lankhorst@linux.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