From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: wangxuewen <18810879172@163.com>,
david@fromorbit.com, qi.zheng@linux.dev,
roman.gushchin@linux.dev, muchun.song@linux.dev,
oe-kbuild-all@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] mm/shrinker: simplify shrinker_memcg_alloc() using guard()
Date: Mon, 18 May 2026 17:36:07 -0700 [thread overview]
Message-ID: <20260518173607.c250f771be2baf92fa471b2d@linux-foundation.org> (raw)
In-Reply-To: <202605151100.lH0pRo2I-lkp@intel.com>
On Fri, 15 May 2026 11:15:40 +0800 kernel test robot <lkp@intel.com> wrote:
> Hi wangxuewen,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on v7.1-rc3]
> [also build test WARNING on linus/master next-20260508]
> [cannot apply to akpm-mm/mm-everything]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/wangxuewen/mm-shrinker-simplify-shrinker_memcg_alloc-using-guard/20260515-014803
> base: v7.1-rc3
> patch link: https://lore.kernel.org/r/20260512085546.368911-1-18810879172%40163.com
> patch subject: [PATCH v1] mm/shrinker: simplify shrinker_memcg_alloc() using guard()
> config: sh-allyesconfig (https://download.01.org/0day-ci/archive/20260515/202605151100.lH0pRo2I-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/20260515/202605151100.lH0pRo2I-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/202605151100.lH0pRo2I-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> mm/shrinker.c: In function 'shrinker_memcg_alloc':
> >> mm/shrinker.c:218:17: warning: unused variable 'ret' [-Wunused-variable]
> 218 | int id, ret = -ENOMEM;
> | ^~~
Something went wrong here - that patch *removes* this definition of
`ret'.
https://lore.kernel.org/20260513075214.2655710-1-18810879172@163.com
next prev parent reply other threads:[~2026-05-19 0:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 8:55 wangxuewen
2026-05-12 9:10 ` Muchun Song
2026-05-13 7:55 ` wangxuewen
2026-05-12 9:12 ` Qi Zheng
2026-05-15 3:15 ` kernel test robot
2026-05-19 0:36 ` Andrew Morton [this message]
2026-05-19 1:31 ` wangxuewen
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=20260518173607.c250f771be2baf92fa471b2d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=18810879172@163.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=muchun.song@linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=qi.zheng@linux.dev \
--cc=roman.gushchin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®