From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Frank van der Linden <fvdl@google.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-unstable 77/88] mm/hugetlb_vmemmap.c:704:17: error: label 'out' used but not defined
Date: Thu, 30 Jan 2025 22:43:03 -0800 [thread overview]
Message-ID: <20250130224303.5964449be385d688996d5dd3@linux-foundation.org> (raw)
In-Reply-To: <202501311312.ZTWda9Ip-lkp@intel.com>
On Fri, 31 Jan 2025 13:29:18 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> head: 495206a68b359eb6117d0860861578113bbb94e7
> commit: 383ad37bda9ba2414ce6abff61fecdc09afc623a [77/88] mm/hugetlb: add pre-HVO framework
> config: x86_64-buildonly-randconfig-001-20250131 (https://download.01.org/0day-ci/archive/20250131/202501311312.ZTWda9Ip-lkp@intel.com/config)
> compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250131/202501311312.ZTWda9Ip-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/202501311312.ZTWda9Ip-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> mm/hugetlb_vmemmap.c: In function '__hugetlb_vmemmap_optimize_folios':
> >> mm/hugetlb_vmemmap.c:704:17: error: label 'out' used but not defined
> 704 | goto out;
> | ^~~~
huh, I shouldn't have pushed that one out. Fixed now, thanks.
prev parent reply other threads:[~2025-01-31 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 5:29 kernel test robot
2025-01-31 6:43 ` Andrew Morton [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=20250130224303.5964449be385d688996d5dd3@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fvdl@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox