From: SeongJae Park <sj@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: SeongJae Park <sj@kernel.org>,
oe-kbuild-all@lists.linux.dev, damon@lists.linux.dev
Subject: Re: [sj:damon/next 45/45] mm/damon/paddr.c:316:30: warning: variable 'last_addr' set but not used
Date: Mon, 20 Jan 2025 13:03:34 -0800 [thread overview]
Message-ID: <20250120210334.44451-1-sj@kernel.org> (raw)
In-Reply-To: <202501191712.rj88Gj15-lkp@intel.com>
On Sun, 19 Jan 2025 17:35:50 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git damon/next
> head: 38bf43ccce488ca872dbc52673c7a2223fb13598
> commit: 38bf43ccce488ca872dbc52673c7a2223fb13598 [45/45] mm/damon/paddr: implement a DAMON operations set for cache address space
> config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20250119/202501191712.rj88Gj15-lkp@intel.com/config)
> compiler: s390-linux-gcc (GCC) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250119/202501191712.rj88Gj15-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/202501191712.rj88Gj15-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> mm/damon/paddr.c: In function '__damon_ca_check_access':
> >> mm/damon/paddr.c:316:30: warning: variable 'last_addr' set but not used [-Wunused-but-set-variable]
> 316 | static unsigned long last_addr;
> | ^~~~~~~~~
Thank you always for nice reports! Just pushed a fix:
https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git/commit/?h=damon/next&id=2e43bb84cc76ee5e1bc1000d161609ee4c279771
Thanks,
SJ
[...]
prev parent reply other threads:[~2025-01-20 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 9:35 [sj:damon/next 45/45] mm/damon/paddr.c:316:30: warning: variable 'last_addr' set but not used kernel test robot
2025-01-20 21:03 ` 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=20250120210334.44451-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--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.