From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Yuan Can <yuancan@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 1683/15331] mm/memcontrol.c:3147:6: warning: no previous prototype for 'hisi_oom_recover'
Date: Sun, 27 Oct 2024 09:21:29 +0800 [thread overview]
Message-ID: <202410270959.J8MWcOrp-lkp@intel.com> (raw)
Hi Weilong,
FYI, the error/warning still remains.
tree: https://gitee.com/openeuler/kernel.git OLK-6.6
head: 9d0af12b79bee784902822ddeec2e1a8cfc18524
commit: b498d9f1bacd40d583c0970cab02ad522127a7e7 [1683/15331] arm64/ascend: Add new enable_oom_killer interface for oom contrl
config: arm64-randconfig-003-20241027 (https://download.01.org/0day-ci/archive/20241027/202410270959.J8MWcOrp-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241027/202410270959.J8MWcOrp-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/202410270959.J8MWcOrp-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/memcontrol.c:3147:6: warning: no previous prototype for 'hisi_oom_recover' [-Wmissing-prototypes]
3147 | void hisi_oom_recover(struct obj_cgroup *objcg)
| ^~~~~~~~~~~~~~~~
vim +/hisi_oom_recover +3147 mm/memcontrol.c
3145
3146 #ifdef CONFIG_ASCEND_OOM
> 3147 void hisi_oom_recover(struct obj_cgroup *objcg)
3148 {
3149 struct mem_cgroup *memcg;
3150
3151 memcg = get_mem_cgroup_from_objcg(objcg);
3152 if (!mem_cgroup_is_root(memcg))
3153 memcg_oom_recover(memcg);
3154 css_put(&memcg->css);
3155 }
3156 #else
3157 static inline void hisi_oom_recover(struct obj_cgroup *objcg) { }
3158 #endif
3159
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-10-27 1:22 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=202410270959.J8MWcOrp-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yuancan@huawei.com \
/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.