From: kernel test robot <lkp@intel.com>
To: SeongJae Park <sj@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 5320/5590] mm/damon/sysfs-schemes.c:1622:32: sparse: sparse: symbol 'damos_sysfs_action_names' was not declared. Should it be static?
Date: Fri, 27 Jun 2025 16:41:02 +0800 [thread overview]
Message-ID: <202506271655.b8yfEZIT-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: ecb259c4f70dd5c83907809f45bf4dc6869961d7
commit: 98c5783c468ce5630a0604c69694d04ccc078c02 [5320/5590] mm/damon/sysfs-schemes: decouple from damos_action
config: hexagon-randconfig-r122-20250627 (https://download.01.org/0day-ci/archive/20250627/202506271655.b8yfEZIT-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project e04c938cc08a90ae60440ce22d072ebc69d67ee8)
reproduce: (https://download.01.org/0day-ci/archive/20250627/202506271655.b8yfEZIT-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/202506271655.b8yfEZIT-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> mm/damon/sysfs-schemes.c:1622:32: sparse: sparse: symbol 'damos_sysfs_action_names' was not declared. Should it be static?
vim +/damos_sysfs_action_names +1622 mm/damon/sysfs-schemes.c
1621
> 1622 struct damos_sysfs_action_name damos_sysfs_action_names[] = {
1623 {
1624 .action = DAMOS_WILLNEED,
1625 .name = "willneed",
1626 },
1627 {
1628 .action = DAMOS_COLD,
1629 .name = "cold",
1630 },
1631 {
1632 .action = DAMOS_PAGEOUT,
1633 .name = "pageout",
1634 },
1635 {
1636 .action = DAMOS_HUGEPAGE,
1637 .name = "hugepage",
1638 },
1639 {
1640 .action = DAMOS_NOHUGEPAGE,
1641 .name = "nohugepage",
1642 },
1643 {
1644 .action = DAMOS_LRU_PRIO,
1645 .name = "lru_prio",
1646 },
1647 {
1648 .action = DAMOS_LRU_DEPRIO,
1649 .name = "lru_deprio",
1650 },
1651 {
1652 .action = DAMOS_MIGRATE_HOT,
1653 .name = "migrate_hot",
1654 },
1655 {
1656 .action = DAMOS_MIGRATE_COLD,
1657 .name = "migrate_cold",
1658 },
1659 {
1660 .action = DAMOS_STAT,
1661 .name = "stat",
1662 },
1663 };
1664
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-06-27 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 8:41 kernel test robot [this message]
2025-06-27 19:57 ` Andrew Morton
2025-06-27 20:11 ` SeongJae Park
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=202506271655.b8yfEZIT-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sj@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