[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d54d4ff-c8a3-145a-7ec5-f32107eda21e@infradead.org>
Date: Tue, 27 Sep 2022 14:33:19 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: paulmck@...nel.org
Cc: broonie@...nel.org,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-um <linux-um@...ts.infradead.org>
Subject: Re: linux-next: Tree for Sep 27 (uml 64-bit or 32-bit: tinyconfig)
On 9/27/22 14:28, Paul E. McKenney wrote:
> On Tue, Sep 27, 2022 at 02:13:29PM -0700, Randy Dunlap wrote:
>>
>>
>> On 9/27/22 13:10, broonie@...nel.org wrote:
>>> Hi all,
>>>
>>> Changes since 20220923:
>>>
>>
>> In file included from ../include/linux/notifier.h:16,
>> from ../include/linux/memory_hotplug.h:7,
>> from ../include/linux/mmzone.h:1244,
>> from ../include/linux/gfp.h:7,
>> from ../include/linux/slab.h:15,
>> from ../include/linux/crypto.h:20,
>> from ../arch/x86/um/shared/sysdep/kernel-offsets.h:5,
>> from ../arch/um/kernel/asm-offsets.c:1:
>> ../include/linux/srcu.h: In function ‘srcu_read_lock_nmisafe’:
>> ../include/linux/srcu.h:181:26: error: implicit declaration of function ‘__srcu_read_lock_nmisafe’; did you mean ‘srcu_read_lock_nmisafe’? [-Werror=implicit-function-declaration]
>> 181 | retval = __srcu_read_lock_nmisafe(ssp, true);
>> | ^~~~~~~~~~~~~~~~~~~~~~~~
>> | srcu_read_lock_nmisafe
>> ../include/linux/srcu.h: In function ‘srcu_read_unlock_nmisafe’:
>> ../include/linux/srcu.h:226:17: error: implicit declaration of function ‘__srcu_read_unlock_nmisafe’; did you mean ‘srcu_read_unlock_nmisafe’? [-Werror=implicit-function-declaration]
>> 226 | __srcu_read_unlock_nmisafe(ssp, idx, true);
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
>> | srcu_read_unlock_nmisafe
>
> Could you please send your .config or tell me how you generated it?
For x86_64 SUBARCH, ARCH=um:
mkdir UML64
make ARCH=um SUBARCH=x86_64 O=UML64 tinyconfig
make ARCH=um SUBARCH=x86_64 O=UML64 all
--
~Randy
Powered by blists - more mailing lists