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 112/124] mm/damon/core.c:1862:25: error: 'c' undeclared
Date: Mon, 9 Feb 2026 09:46:20 -0800 [thread overview]
Message-ID: <20260209174621.39775-1-sj@kernel.org> (raw)
In-Reply-To: <202602100155.sDqMXews-lkp@intel.com>
On Tue, 10 Feb 2026 01:35:06 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git damon/next
> head: a8c204a2a82057d70dd8944476dd043dc52561ed
> commit: 7fdffc23ed84ea44a9f15f71d15b00a94f326acd [112/124] mm/damon/core: unify damon_warn_fix_nr_accesses_corruption() with damon_verify_reset_aggregated()
> config: sh-allyesconfig (https://download.01.org/0day-ci/archive/20260210/202602100155.sDqMXews-lkp@intel.com/config)
> compiler: sh4-linux-gcc (GCC) 15.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260210/202602100155.sDqMXews-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/202602100155.sDqMXews-lkp@intel.com/
>
> Note: the sj/damon/next HEAD a8c204a2a82057d70dd8944476dd043dc52561ed builds fine.
> It only hurts bisectability.
Thank you for this report. Seems this is same to another one, that a fix [1]
has pushed a few hours ago. I understand it is still making bisect
complicated, because the fix was made as a separate commit. I will squash the
fix to the broken commit soon.
[1] https://lore.kernel.org/20260209151322.54520-1-sj@kernel.org
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-02-09 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 17:35 [sj:damon/next 112/124] mm/damon/core.c:1862:25: error: 'c' undeclared kernel test robot
2026-02-09 17:46 ` 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=20260209174621.39775-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.