[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <048cef07-ad4b-8788-94a4-e144de731ab6@infradead.org>
Date: Tue, 28 Jul 2020 15:39:21 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: 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 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
Powered by blists - more mailing lists