Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: broonie@kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-next@vger.kernel.org, mhocko@suse.cz,
	mm-commits@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: mmotm 2020-07-27-18-18 uploaded (mm/page_alloc.c)
Date: Tue, 28 Jul 2020 19:04:09 -0700	[thread overview]
Message-ID: <bdd0b49f-2cdd-02e1-3c91-d96b4f806490@infradead.org> (raw)
In-Reply-To: <20200728184419.4b137162844987c9199542bb@linux-foundation.org>

On 7/28/20 6:44 PM, Andrew Morton wrote:
> On Tue, 28 Jul 2020 15:39:21 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> 
>> On 7/28/20 2:55 PM, Andrew Morton wrote:
>>> On Tue, 28 Jul 2020 05:33:58 -0700 Randy Dunlap <rdunlap@infradead.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.
> 
> Well the first thing I hit was
> 
> Support for big SMP systems with more than 8 CPUs (X86_BIGSMP) [N/y/?] (NEW) 
> 
> and your .config doesn't mention that.

It's an x86_32 symbol and my config was for x86_64.


> make mrproper
> cp ~/config-randy .config
> make oldconfig

make ARCH=x86_64 oldconfig

HTH.
-- 
~Randy


  reply	other threads:[~2020-07-29  2:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200723211432.b31831a0df3bc2cbdae31b40@linux-foundation.org>
2020-07-28  1:19 ` mmotm 2020-07-27-18-18 uploaded Andrew Morton
2020-07-28  2:14   ` Stephen Rothwell
     [not found]   ` <CGME20200728032310epcas5p27226ae967b93325ca145e70a14a8bdf8@epcas5p2.samsung.com>
     [not found]     ` <c99c3cef-1b03-0adf-62a6-373e692425b5@infradead.org>
2020-07-28  8:23       ` mmotm 2020-07-27-18-18 uploaded (drivers/scsi/ufs/: SCSI_UFS_EXYNOS) Alim Akhtar
     [not found]   ` <ae87385b-f830-dbdf-ebc7-1afb82a7fed0@infradead.org>
2020-07-28 21:55     ` mmotm 2020-07-27-18-18 uploaded (mm/page_alloc.c) Andrew Morton
2020-07-28 22:20       ` Stephen Rothwell
2020-07-28 22:31         ` Andrew Morton
2020-07-29 14:18           ` Michael S. Tsirkin
2020-07-29 14:38             ` David Hildenbrand
2020-07-29 16:14               ` David Hildenbrand
2020-07-29 17:29                 ` Randy Dunlap
2020-07-28 22:39       ` Randy Dunlap
2020-07-29  1:43         ` Nathan Chancellor
2020-07-29  1:44         ` Andrew Morton
2020-07-29  2:04           ` Randy Dunlap [this message]
2020-07-29 14:09           ` make oldconfig (Re: mmotm 2020-07-27-18-18 uploaded (mm/page_alloc.c)) Alexey Dobriyan
2020-07-31 23:46 ` mmotm 2020-07-31-16-45 uploaded Andrew Morton

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=bdd0b49f-2cdd-02e1-3c91-d96b4f806490@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --subject='Re: mmotm 2020-07-27-18-18 uploaded (mm/page_alloc.c)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).