From: kernel test robot <lkp@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev, matthew.d.roper@intel.com
Subject: Re: [PATCH 3/4] drm/xe: Drop usage of TIMESTAMP_OVERRIDE
Date: Fri, 21 Feb 2025 12:25:43 +0800 [thread overview]
Message-ID: <202502211245.wEClyBRb-lkp@intel.com> (raw)
In-Reply-To: <20250221003843.443559-9-matthew.d.roper@intel.com>
Hi Matt,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20250220]
[cannot apply to drm-xe/drm-xe-next v6.14-rc3 v6.14-rc2 v6.14-rc1 linus/master v6.14-rc3]
[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/Matt-Roper/drm-i915-display-Make-refclk-fetching-logic-reusable/20250221-084058
base: next-20250220
patch link: https://lore.kernel.org/r/20250221003843.443559-9-matthew.d.roper%40intel.com
patch subject: [PATCH 3/4] drm/xe: Drop usage of TIMESTAMP_OVERRIDE
config: i386-buildonly-randconfig-003-20250221 (https://download.01.org/0day-ci/archive/20250221/202502211245.wEClyBRb-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250221/202502211245.wEClyBRb-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/202502211245.wEClyBRb-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/xe/xe_irq.c:12:
>> drivers/gpu/drm/xe/display/xe_display.h:77:12: warning: 'xe_display_get_refclk' defined but not used [-Wunused-function]
77 | static u32 xe_display_get_refclk(struct xe_device *xe) { return 38400; }
| ^~~~~~~~~~~~~~~~~~~~~
vim +/xe_display_get_refclk +77 drivers/gpu/drm/xe/display/xe_display.h
76
> 77 static u32 xe_display_get_refclk(struct xe_device *xe) { return 38400; }
78
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-02-21 4:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 0:38 [PATCH 0/4] Stop accessing display TIMESTAMP_OVERRIDE in GT code Matt Roper
2025-02-21 0:38 ` [PATCH 1/4] drm/i915/display: Make refclk fetching logic reusable Matt Roper
2025-02-24 9:13 ` Jani Nikula
2025-02-24 13:31 ` Vivekanandan, Balasubramani
2025-02-21 0:38 ` [PATCH 2/4] drm/i915/gt: Replace TIMESTAMP_OVERRIDE readout Matt Roper
2025-02-24 13:55 ` Vivekanandan, Balasubramani
2025-02-21 0:38 ` [PATCH 3/4] drm/xe: Drop usage of TIMESTAMP_OVERRIDE Matt Roper
2025-02-21 3:35 ` Lucas De Marchi
2025-02-21 4:25 ` kernel test robot [this message]
2025-02-24 14:13 ` Vivekanandan, Balasubramani
2025-02-21 0:38 ` [PATCH 4/4] drm/xe/sriov: Drop TIMESTAMP_OVERRIDE from Xe2 runtime regs Matt Roper
2025-02-21 0:44 ` ✓ CI.Patch_applied: success for Stop accessing display TIMESTAMP_OVERRIDE in GT code Patchwork
2025-02-21 0:44 ` ✓ CI.checkpatch: " Patchwork
2025-02-21 0:46 ` ✓ CI.KUnit: " Patchwork
2025-02-21 1:02 ` ✓ CI.Build: " Patchwork
2025-02-21 1:05 ` ✓ CI.Hooks: " Patchwork
2025-02-21 1:06 ` ✗ CI.checksparse: warning " Patchwork
2025-02-21 1:26 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-21 2:00 ` ✗ Fi.CI.SPARSE: warning " Patchwork
2025-02-21 2:20 ` ✓ i915.CI.BAT: success " Patchwork
2025-02-21 4:17 ` ✗ i915.CI.Full: failure " Patchwork
2025-02-21 17:01 ` ✗ Xe.CI.Full: " 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=202502211245.wEClyBRb-lkp@intel.com \
--to=lkp@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.