All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Wupeng Ma <mawupeng1@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 3195/3195] drivers/base/arch_numa.c:194:12: warning: no previous prototype for function 'node_reclaim_distance_setup'
Date: Sat, 15 Nov 2025 14:01:02 +0800	[thread overview]
Message-ID: <202511151309.KnZraqS3-lkp@intel.com> (raw)

tree:   https://gitee.com/openeuler/kernel.git OLK-6.6
head:   5f56814d65eaa85e3277534a309f4e7b4f095412
commit: 5e5d40e65cb55e4699c9879674a004f246606a8d [3195/3195] arch_numa: Make node reclaim distance adjustment always available
config: arm64-randconfig-002-20251115 (https://download.01.org/0day-ci/archive/20251115/202511151309.KnZraqS3-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/20251115/202511151309.KnZraqS3-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/202511151309.KnZraqS3-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/base/arch_numa.c:194:12: warning: no previous prototype for function 'node_reclaim_distance_setup' [-Wmissing-prototypes]
     194 | int __init node_reclaim_distance_setup(char *str)
         |            ^
   drivers/base/arch_numa.c:194:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
     194 | int __init node_reclaim_distance_setup(char *str)
         | ^
         | static 
   1 warning generated.

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for HALTPOLL_CPUIDLE
   Depends on [n]: CPU_IDLE [=n] && ARCH_CPUIDLE_HALTPOLL [=y] && ARCH_HAS_OPTIMIZED_POLL [=y]
   Selected by [y]:
   - ARM64 [=y]


vim +/node_reclaim_distance_setup +194 drivers/base/arch_numa.c

   192	
   193	#define DISTANCE_MAX		(1 << DISTANCE_BITS)
 > 194	int __init node_reclaim_distance_setup(char *str)
   195	{
   196		int val;
   197	
   198		if (kstrtoint(str, 0, &val))
   199			return -EINVAL;
   200	
   201		if (val < LOCAL_DISTANCE || val >= DISTANCE_MAX)
   202			return -EINVAL;
   203	
   204		if (val != RECLAIM_DISTANCE) {
   205			node_reclaim_distance = val;
   206			pr_info("Force set node_reclaim_distance to %d\n", val);
   207		}
   208	
   209		return 0;
   210	}
   211	early_param("node_reclaim_distance", node_reclaim_distance_setup);
   212	

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

                 reply	other threads:[~2025-11-15  6:01 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=202511151309.KnZraqS3-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kernel@openeuler.org \
    --cc=mawupeng1@huawei.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.