linux-kernel - Re: linux-next: Tree for Feb 27 (drivers/of/unittest.c)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 27 Feb 2020 15:47:42 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Frank Rowand <frowand.list@...il.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        devicetree@...r.kernel.org, Rob Herring <robh+dt@...nel.org>
Subject: Re: linux-next: Tree for Feb 27 (drivers/of/unittest.c)

On 2/27/20 1:12 PM, Frank Rowand wrote:
> Hi Randy,
> 
> On 2/27/20 10:23 AM, Randy Dunlap wrote:
>> On 2/26/20 8:22 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20200226:
>>>
>>
>> on x86_64:
>>
>> # CONFIG_GPIOLIB is not set
>>
>> ../drivers/of/unittest.c: In function ‘unittest_gpio_probe’:
>> ../drivers/of/unittest.c:94:14: error: ‘struct gpio_chip’ has no member named ‘of_node’
>>   devptr->chip.of_node = pdev->dev.of_node;
>>               ^
>> In file included from ../include/linux/kernel.h:15:0,
>>                  from ../include/asm-generic/bug.h:19,
>>                  from ../arch/x86/include/asm/bug.h:83,
>>                  from ../include/linux/bug.h:5,
>>                  from ../include/linux/mmdebug.h:5,
>>                  from ../include/linux/mm.h:9,
>>                  from ../include/linux/memblock.h:13,
>>                  from ../drivers/of/unittest.c:8:
>> ../drivers/of/unittest.c:103:73: error: ‘struct gpio_chip’ has no member named ‘of_node’
>>     "gpiochip_add_data() for node @%pOF failed, ret = %d\n", devptr->chip.of_node, ret);
>>                                                                          ^
>>
>> Full randconfig file is attached.
>>
> 
> I am trying to build a kernel with the randconfig you provided.
> 
> I am trying to figure out how to build with the exact configuration,
> but every way I've tried to build modifies the .config file.
> 
> Do you have any pointers to info on how to get the build system
> to use exactly the .config without modification?
> 
> (Just in case it is pertinent, I am using Linux 5.6-rc1 instead
> of -next.)

Hi Frank,

Yeah, I can't get 5.6-rc1 to use that same .config file either.
There are too many differences from rc1 to rc3+next and any
'make' command will automatically run oldconfig (or silentoldconfig)
to update the .config file.

-- 
~Randy