From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: drivers/ptp/ptp_vmclock.c:392:24: warning: unused variable 'st'
Date: Mon, 04 May 2026 01:45:48 +0800 [thread overview]
Message-ID: <202605040151.8XwAzkix-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "bisect to a FBC not belonging to original linux-review patches: branch: linux-review/Arthur-Kiyanovski/ptp-Add-ioctls-for-PHC-timestamps-with-quality-attributes/20260501-120618, commit: df313359b943b68d54c834330766e4f1d3afade0"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Arthur Kiyanovski <akiyano@amazon.com>
CC: 0day robot <lkp@intel.com>
tree: https://github.com/intel-lab-lkp/linux/commits/Arthur-Kiyanovski/ptp-Add-ioctls-for-PHC-timestamps-with-quality-attributes/20260501-120618
head: 02bdf82208619595607dd1a4004fa7b729f7b43a
commit: df313359b943b68d54c834330766e4f1d3afade0 ptp: ptp_vmclock: Implement attributes ioctls
date: 3 days ago
:::::: branch date: 3 days ago
:::::: commit date: 3 days ago
config: arm64-randconfig-001-20260503 (https://download.01.org/0day-ci/archive/20260504/202605040151.8XwAzkix-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260504/202605040151.8XwAzkix-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/r/202605040151.8XwAzkix-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/ptp/ptp_vmclock.c: In function 'ptp_vmclock_do_getcrosststamp':
>> drivers/ptp/ptp_vmclock.c:392:24: warning: unused variable 'st' [-Wunused-variable]
struct vmclock_state *st = vctx->st;
^~
vim +/st +392 drivers/ptp/ptp_vmclock.c
20503272422693d David Woodhouse 2024-10-06 388
df313359b943b68 Arthur Kiyanovski 2026-04-30 389 static int ptp_vmclock_do_getcrosststamp(struct vmclock_crosststamp_ctx *vctx,
20503272422693d David Woodhouse 2024-10-06 390 struct system_device_crosststamp *xtstamp)
20503272422693d David Woodhouse 2024-10-06 391 {
df313359b943b68 Arthur Kiyanovski 2026-04-30 @392 struct vmclock_state *st = vctx->st;
df313359b943b68 Arthur Kiyanovski 2026-04-30 393 int ret = get_device_system_crosststamp(ptp_vmclock_get_time_fn, vctx,
20503272422693d David Woodhouse 2024-10-06 394 NULL, xtstamp);
20503272422693d David Woodhouse 2024-10-06 395 #ifdef SUPPORT_KVMCLOCK
20503272422693d David Woodhouse 2024-10-06 396 /*
20503272422693d David Woodhouse 2024-10-06 397 * On x86, the KVM clock may be used for the system time. We can
20503272422693d David Woodhouse 2024-10-06 398 * actually convert a TSC reading to that, and return a paired
20503272422693d David Woodhouse 2024-10-06 399 * timestamp that get_device_system_crosststamp() *can* handle.
20503272422693d David Woodhouse 2024-10-06 400 */
20503272422693d David Woodhouse 2024-10-06 401 if (ret == -ENODEV) {
20503272422693d David Woodhouse 2024-10-06 402 struct system_time_snapshot systime_snapshot;
20503272422693d David Woodhouse 2024-10-06 403
20503272422693d David Woodhouse 2024-10-06 404 ktime_get_snapshot(&systime_snapshot);
20503272422693d David Woodhouse 2024-10-06 405
20503272422693d David Woodhouse 2024-10-06 406 if (systime_snapshot.cs_id == CSID_X86_TSC ||
20503272422693d David Woodhouse 2024-10-06 407 systime_snapshot.cs_id == CSID_X86_KVM_CLK) {
20503272422693d David Woodhouse 2024-10-06 408 WRITE_ONCE(st->sys_cs_id, systime_snapshot.cs_id);
20503272422693d David Woodhouse 2024-10-06 409 ret = get_device_system_crosststamp(ptp_vmclock_get_time_fn,
df313359b943b68 Arthur Kiyanovski 2026-04-30 410 vctx, NULL, xtstamp);
20503272422693d David Woodhouse 2024-10-06 411 }
20503272422693d David Woodhouse 2024-10-06 412 }
20503272422693d David Woodhouse 2024-10-06 413 #endif
20503272422693d David Woodhouse 2024-10-06 414 return ret;
20503272422693d David Woodhouse 2024-10-06 415 }
20503272422693d David Woodhouse 2024-10-06 416
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-03 17:47 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=202605040151.8XwAzkix-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.