Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: linux-next: build warning after merge of the pm tree
Date: Tue, 15 Oct 2019 11:23:33 +0300
Message-ID: <20191015082333.GV32742@smile.fi.intel.com> (raw)
In-Reply-To: <20191015100855.31b8a3d5@canb.auug.org.au>

On Tue, Oct 15, 2019 at 10:08:55AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the pm tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> In file included from include/linux/irqchip.h:14,
>                  from arch/arm/kernel/irq.c:26:
> include/linux/acpi.h:682:31: warning: 'struct acpi_device' declared inside parameter list will not be visible outside of this definition or declaration
>   682 | acpi_dev_hid_uid_match(struct acpi_device *adev, const char *hid2, const char *uid2)
>       |                               ^~~~~~~~~~~
> 
> and many more.
> 
> Introduced by commit
> 
>   d1748b57dc88 ("ACPI / utils: Introduce acpi_dev_hid_uid_match() helper")
> 
> CONFIG_ACPI is not set for this build.

I'm puzzled. Why it builds before?

Another function has struct acpi_device *adev in its prototype and it was
before above mentioned commit.


-- 
With Best Regards,
Andy Shevchenko



  parent reply index

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 23:08 Stephen Rothwell
2019-10-14 23:16 ` linux-next: build failure after merge of the pm tree (Was: linux-next: build warning after merge of the pm tree) Stephen Rothwell
2019-10-15 10:04   ` Rafael J. Wysocki
2019-10-16  9:15     ` Geert Uytterhoeven
2019-10-16  9:33       ` Andy Shevchenko
2019-10-15  8:23 ` Andy Shevchenko [this message]
2019-10-15  9:41   ` linux-next: build warning after merge of the pm tree Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2020-01-19 23:40 Stephen Rothwell
     [not found] <201907111346291954773@zte.com.cn>
2019-07-11 12:26 ` Rafael J. Wysocki
2019-07-11  1:31 Stephen Rothwell
2019-01-23 23:45 Stephen Rothwell
2018-07-30  2:00 Stephen Rothwell
2018-07-30  7:24 ` Sakari Ailus
2018-07-30  7:30   ` jacopo mondi
2018-07-31  0:39   ` Stephen Rothwell
2018-06-08  0:30 Stephen Rothwell
2018-06-08  9:14 ` Rafael J. Wysocki
2018-04-09  1:24 Stephen Rothwell
2018-04-10  7:05 ` Rafael J. Wysocki
2016-11-13 23:40 Stephen Rothwell
2016-11-14  0:03 ` Rafael J. Wysocki
2016-11-14  8:49   ` Akshay Adiga
2014-11-17  2:44 Stephen Rothwell
2014-11-17 11:31 ` Paul Bolle
2014-11-17 23:14   ` Rafael J. Wysocki
2014-11-17 23:45     ` Paul Bolle
2014-11-18  0:34       ` Rafael J. Wysocki
2014-10-29  2:51 Stephen Rothwell
2014-10-29 14:55 ` Rafael J. Wysocki
2014-10-29 15:23   ` Fengguang Wu
2014-10-29 15:56     ` Rafael J. Wysocki

Reply instructions:

You may reply publically 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=20191015082333.GV32742@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    --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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git