linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: linux-next: Tree for Feb 27 (drivers/of/unittest.c)
Date: Thu, 27 Feb 2020 15:12:22 -0600	[thread overview]
Message-ID: <0bd9179f-c448-c40d-f520-d568547bc810@gmail.com> (raw)
In-Reply-To: <ed57c797-1d40-0786-2cdc-adae7047a86f@infradead.org>

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.)

-Frank

  parent reply	other threads:[~2020-02-27 21:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27  4:22 linux-next: Tree for Feb 27 Stephen Rothwell
2020-02-27 16:23 ` linux-next: Tree for Feb 27 (drivers/of/unittest.c) Randy Dunlap
2020-02-27 19:36   ` Frank Rowand
2020-02-27 21:12   ` Frank Rowand [this message]
2020-02-27 23:47     ` Randy Dunlap
2020-02-27 16:34 ` linux-next: Tree for Feb 27 (sound/soc/codecs/: SND_SOC_MAX98357A) Randy Dunlap

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=0bd9179f-c448-c40d-f520-d568547bc810@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).