linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: "Jakub Matěna" <matenajakub@gmail.com>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	"Vlastimil Babka" <vbabka@suse.cz>
Subject: Re: [akpm-mm:mm-unstable 102/232] mm/mmap.c:1094:9: error: 'area' undeclared
Date: Sun, 3 Jul 2022 22:17:58 -0700	[thread overview]
Message-ID: <20220703221758.619e283069ac685ce9c321c2@linux-foundation.org> (raw)
In-Reply-To: <202207041144.WB9XlrTL-lkp@intel.com>

On Mon, 4 Jul 2022 11:42:55 +0800 kernel test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> head:   ff9d7221f1fc9bddb4f71f7501154c68b6942b9b
> commit: 24a134b0c0a857bbf193eb7b3d8fcbbf77517c5f [102/232] mm: refactor of vma_merge()
> config: powerpc-allnoconfig (https://download.01.org/0day-ci/archive/20220704/202207041144.WB9XlrTL-lkp@intel.com/config)
> compiler: powerpc-linux-gcc (GCC) 11.3.0
> reproduce (this is a W=1 build):
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/commit/?id=24a134b0c0a857bbf193eb7b3d8fcbbf77517c5f
>         git remote add akpm-mm https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git
>         git fetch --no-tags akpm-mm mm-unstable
>         git checkout 24a134b0c0a857bbf193eb7b3d8fcbbf77517c5f
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=powerpc SHELL=/bin/bash
> 
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
>    mm/mmap.c: In function 'vma_merge':
> >> mm/mmap.c:1094:9: error: 'area' undeclared (first use in this function)
>     1094 |         area = next;
>          |         ^~~~

Thanks, that was a merge messup.  Already fixed.  You evidently pulled
during the half-hour window when it wasn't :(




      reply	other threads:[~2022-07-04  5:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04  3:42 kernel test robot
2022-07-04  5:17 ` 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=20220703221758.619e283069ac685ce9c321c2@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=matenajakub@gmail.com \
    --cc=vbabka@suse.cz \
    /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