All of lore.kernel.org
 help / color / mirror / Atom feed
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 130/142] samples/damon/mtier.c:78:30: warning: unused variable 'region'
Date: Tue, 17 Feb 2026 07:20:14 -0800	[thread overview]
Message-ID: <20260217152015.80806-1-sj@kernel.org> (raw)
In-Reply-To: <202602171530.NsLdPVOF-lkp@intel.com>

On Tue, 17 Feb 2026 15:33:25 +0800 kernel test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git damon/next
> head:   53a936b437ade97f957569534f1460d23883b94f
> commit: 52639cde20a9887c5df4acc55fb51a4f48a1644d [130/142] samples/damon/mtier: replace damon_add_region() with damon_set_regions()
> config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20260217/202602171530.NsLdPVOF-lkp@intel.com/config)
> compiler: m68k-linux-gcc (GCC) 15.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260217/202602171530.NsLdPVOF-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/202602171530.NsLdPVOF-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>):
> 
>    samples/damon/mtier.c: In function 'damon_sample_mtier_build_ctx':
> >> samples/damon/mtier.c:78:30: warning: unused variable 'region' [-Wunused-variable]
>       78 |         struct damon_region *region;
>          |                              ^~~~~~

Thank you for this report!  I just added a fix for this to my tree.


Thanks,
SJ

[...]

      reply	other threads:[~2026-02-17 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17  7:33 [sj:damon/next 130/142] samples/damon/mtier.c:78:30: warning: unused variable 'region' kernel test robot
2026-02-17 15:20 ` 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=20260217152015.80806-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.