[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200729014333.GA33042@ubuntu-n2-xlarge-x86>
Date: Tue, 28 Jul 2020 18:43:33 -0700
From: Nathan Chancellor <natechancellor@...il.com>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, broonie@...nel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-next@...r.kernel.org, mhocko@...e.cz,
mm-commits@...r.kernel.org, sfr@...b.auug.org.au
Subject: Re: mmotm 2020-07-27-18-18 uploaded (mm/page_alloc.c)
On Tue, Jul 28, 2020 at 03:39:21PM -0700, Randy Dunlap wrote:
> On 7/28/20 2:55 PM, Andrew Morton wrote:
> > On Tue, 28 Jul 2020 05:33:58 -0700 Randy Dunlap <rdunlap@...radead.org> wrote:
> >
> >> On 7/27/20 6:19 PM, Andrew Morton wrote:
> >>> The mm-of-the-moment snapshot 2020-07-27-18-18 has been uploaded to
> >>>
> >>> http://www.ozlabs.org/~akpm/mmotm/
>
>
> >> on x86_64:
> >>
> >> ../mm/page_alloc.c:8355:48: warning: ‘struct compact_control’ declared inside parameter list will not be visible outside of this definition or declaration
> >> static int __alloc_contig_migrate_range(struct compact_control *cc,
> >> ^~~~~~~~~~~~~~~
> >
> > As is usually the case with your reports, I can't figure out how to
> > reproduce it. I copy then .config, run `make oldconfig' (need to hit
> > enter a zillion times because the .config is whacky) then the build
> > succeeds. What's the secret?
>
> I was not aware that there was a problem. cp .config and make oldconfig
> should be sufficient -- and I don't understand why you would need to hit
> enter many times.
>
> I repeated this on my system without having to answer any oldconfig prompts
> and still got build errors.
>
> There is no secret that I know of, but it would be good to get to the
> bottom of this problem.
>
> --
> ~Randy
>
I usually do 'olddefconfig', which is the same as oldconfig but it
selects the default value of the symbols that are new. This usually
happens for me if I am flipping around in different trees like mainline
and next, where there might be new or different symbols between them.
Cheers,
Nathan
Powered by blists - more mailing lists