From: sj@kernel.org
To: kernel test robot <lkp@intel.com>
Cc: SeongJae Park <sj@kernel.org>, oe-kbuild-all@lists.linux.dev
Subject: Re: [sj:damon/next 25/28] mm/damon/sysfs-schemes.c:1869:6: warning: no previous prototype for 'damos_sysfs_tried_regions_reset_update_status'
Date: Sun, 1 Oct 2023 16:08:28 +0000 [thread overview]
Message-ID: <20231001160828.47310-1-sj@kernel.org> (raw)
In-Reply-To: <202310010851.UTmHwpyH-lkp@intel.com>
Hi robot,
On Sun, 1 Oct 2023 08:50:48 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git damon/next
> head: ee9e834252d5110f424abdef73f776cd4dc5ceae
> commit: d3dfc5443e1f05dd03955ba5fe214812d0219395 [25/28] mm/damon/sysfs-schemes: update tried regions for only one apply interval
> config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20231001/202310010851.UTmHwpyH-lkp@intel.com/config)
> compiler: alpha-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231001/202310010851.UTmHwpyH-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/202310010851.UTmHwpyH-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> mm/damon/sysfs-schemes.c:127:60: error: field 'update_status' has incomplete type
> 127 | enum damos_sysfs_tried_regions_reset_update_status update_status;
> | ^~~~~~~~~~~~~
> >> mm/damon/sysfs-schemes.c:1869:6: warning: no previous prototype for 'damos_sysfs_tried_regions_reset_update_status' [-Wmissing-prototypes]
> 1869 | void damos_sysfs_tried_regions_reset_update_status(struct damon_ctx *ctx)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> mm/damon/sysfs-schemes.c: In function 'damos_sysfs_tried_regions_reset_update_status':
> mm/damon/sysfs-schemes.c:1876:17: error: 'sysfs_Schemes' undeclared (first use in this function); did you mean 'sysfs_schemes'?
> 1876 | sysfs_Schemes->schemes_arr[i]->tried_regions->update_status =
> | ^~~~~~~~~~~~~
> | sysfs_schemes
> mm/damon/sysfs-schemes.c:1876:17: note: each undeclared identifier is reported only once for each function it appears in
Thank you for this report. I made a fix for this as a followup commit[1]. I
will squash the fix into the original broken commit and push by today.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git/commit/?h=damon/next&id=ff3d1bf4122213fbcae73b075149e7cc3f5c0f34
Thanks,
SJ
>
>
> vim +/damos_sysfs_tried_regions_reset_update_status +1869 mm/damon/sysfs-schemes.c
>
> 1868
> > 1869 void damos_sysfs_tried_regions_reset_update_status(struct damon_ctx *ctx)
> 1870 {
> 1871 struct damon_sysfs_schemes *sysfs_schemes =
> 1872 damon_sysfs_schemes_for_damos_callback;
> 1873 int i;
> 1874
> 1875 for (i = 0; i < sysfs_schemes->nr; i++)
> 1876 sysfs_Schemes->schemes_arr[i]->tried_regions->update_status =
> 1877 damos_tried_region_update_idle;
> 1878 }
> 1879
>
prev parent reply other threads:[~2023-10-01 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 0:50 [sj:damon/next 25/28] mm/damon/sysfs-schemes.c:1869:6: warning: no previous prototype for 'damos_sysfs_tried_regions_reset_update_status' kernel test robot
2023-10-01 16:08 ` sj [this message]
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=20231001160828.47310-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=lkp@intel.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.