linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: 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>,
	Denis Turischev <denis@compulab.co.il>,
	Lee Jones <lee.jones@linaro.org>
Subject: Re: linux-next: Tree for Mar 26 (drivers/mfd/lpc_sch.c)
Date: Fri, 26 Mar 2021 11:26:39 -0700	[thread overview]
Message-ID: <1833e29a-3d16-7041-dd75-784ae4e07faf@infradead.org> (raw)
In-Reply-To: <39a89498-6b81-4d4c-503f-c87805ca620a@infradead.org>

On 3/26/21 11:20 AM, Randy Dunlap wrote:
> On 3/26/21 1:34 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20210325:
>>
> 
> on i386 or x86_64:
> aha:
> # CONFIG_PCI is not set
> 
> 
> ../drivers/mfd/lpc_sch.c:204:1: warning: data definition has no type or storage class
>  module_pci_driver(lpc_sch_driver);
>  ^~~~~~~~~~~~~~~~~
> ../drivers/mfd/lpc_sch.c:204:1: error: type defaults to ‘int’ in declaration of ‘module_pci_driver’ [-Werror=implicit-int]
> ../drivers/mfd/lpc_sch.c:204:1: warning: parameter names (without types) in function declaration
> ../drivers/mfd/lpc_sch.c:197:26: warning: ‘lpc_sch_driver’ defined but not used [-Wunused-variable]
>  static struct pci_driver lpc_sch_driver = {
>                           ^~~~~~~~~~~~~~
> 
> 
> Full x86_64 randconfig file is attached.

This is the root of the problem I think:

WARNING: unmet direct dependencies detected for LPC_SCH
  Depends on [n]: HAS_IOMEM [=y] && PCI [=n]
  Selected by [m]:
  - GPIO_SCH [=m] && GPIOLIB [=y] && X86 [=y] && (X86 [=y] || COMPILE_TEST [=y]) && ACPI [=y]


Denis, that still looks like it's your territory.

thanks.
-- 
~Randy


      reply	other threads:[~2021-03-26 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26  8:34 linux-next: Tree for Mar 26 Stephen Rothwell
2021-03-26 18:20 ` linux-next: Tree for Mar 26 (drivers/mfd/lpc_sch.c) Randy Dunlap
2021-03-26 18:26   ` Randy Dunlap [this message]

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=1833e29a-3d16-7041-dd75-784ae4e07faf@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=denis@compulab.co.il \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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).