From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/urgent] BUILD SUCCESS WITH WARNING 4a35d2b5254af89595fd90dae9ee0c8f990a148d
Date: Tue, 01 Jul 2025 06:02:50 +0800 [thread overview]
Message-ID: <202507010638.tdY9gY6N-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
branch HEAD: 4a35d2b5254af89595fd90dae9ee0c8f990a148d x86/sev: Use TSC_FACTOR for Secure TSC frequency calculation
Warning (recently discovered and may have been fixed):
https://lore.kernel.org/oe-kbuild-all/202507010218.3O5Ge0Xt-lkp@intel.com
arch/x86/coco/sev/core.c:2170:30: warning: variable 'dummy' set but not used [-Wunused-but-set-variable]
Warning ids grouped by kconfigs:
recent_errors
`-- x86_64-allyesconfig
`-- arch-x86-coco-sev-core.c:warning:variable-dummy-set-but-not-used
elapsed time: 730m
configs tested: 20
configs skipped: 126
tested configs:
i386 allmodconfig gcc-12
i386 allnoconfig gcc-12
i386 allyesconfig gcc-12
i386 buildonly-randconfig-001-20250630 clang-20
i386 buildonly-randconfig-002-20250630 gcc-12
i386 buildonly-randconfig-003-20250630 clang-20
i386 buildonly-randconfig-004-20250630 gcc-12
i386 buildonly-randconfig-005-20250630 gcc-12
i386 buildonly-randconfig-006-20250630 clang-20
i386 defconfig clang-20
x86_64 allnoconfig clang-20
x86_64 allyesconfig clang-20
x86_64 buildonly-randconfig-001-20250630 gcc-12
x86_64 buildonly-randconfig-002-20250630 clang-20
x86_64 buildonly-randconfig-003-20250630 clang-20
x86_64 buildonly-randconfig-004-20250630 clang-20
x86_64 buildonly-randconfig-005-20250630 gcc-12
x86_64 buildonly-randconfig-006-20250630 gcc-12
x86_64 defconfig gcc-11
x86_64 rhel-9.4-rust clang-18
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-06-30 22:03 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=202507010638.tdY9gY6N-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®