From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>, kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [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 13:11:22 -0700 [thread overview]
Message-ID: <20250627201122.53436-1-sj@kernel.org> (raw)
In-Reply-To: <20250627125731.19f70c310cb4f315177e41e6@linux-foundation.org>
On Fri, 27 Jun 2025 12:57:31 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 27 Jun 2025 16:41:02 +0800 kernel test robot <lkp@intel.com> wrote:
[...]
> > 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?
>
> Thanks.
>
> --- a/mm/damon/sysfs-schemes.c~mm-damon-sysfs-schemes-decouple-from-damos_action-fix
> +++ a/mm/damon/sysfs-schemes.c
> @@ -1619,7 +1619,7 @@ struct damos_sysfs_action_name {
> char *name;
> };
>
> -struct damos_sysfs_action_name damos_sysfs_action_names[] = {
> +static struct damos_sysfs_action_name damos_sysfs_action_names[] = {
> {
> .action = DAMOS_WILLNEED,
> .name = "willneed",
> _
Thank you Andrew. I posted a same fix[1] but forgot noting that here. Since
it is same to yours and yours is already added to mm tree, let's keep using
yours unless you mind.
FWIW,
Reviewed-by: SeongJae Park <sj@kernel.org>
[1] https://lore.kernel.org/20250627162806.50589-1-sj@kernel.org
Thanks,
SJ
prev parent reply other threads:[~2025-06-27 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 8:41 [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? kernel test robot
2025-06-27 19:57 ` Andrew Morton
2025-06-27 20:11 ` SeongJae Park [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=20250627201122.53436-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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.