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>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	ACPI Devel Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: linux-next: Tree for Apr 3 (acpi_dev_get_first_match*)
Date: Wed, 3 Apr 2019 08:20:15 -0700	[thread overview]
Message-ID: <532f66c8-4c25-10d3-d119-71f3c8f82edd@infradead.org> (raw)
In-Reply-To: <20190403192407.13a99513@canb.auug.org.au>

On 4/3/19 1:24 AM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20190402:
> 

on i386 or x86_64:

The patch(es) that change acpi_dev_get_first_match_name() to
acpi_dev_get_first_match_dev() have a problem when CONFIG_ACPI is not set/enabled.


../drivers/gpio/gpio-merrifield.c: In function ‘mrfld_gpio_get_pinctrl_dev_name’:
../drivers/gpio/gpio-merrifield.c:388:19: error: dereferencing pointer to incomplete type
   put_device(&adev->dev);
                   ^

../drivers/extcon/extcon-axp288.c: In function ‘axp288_extcon_probe’:
../drivers/extcon/extcon-axp288.c:363:20: error: dereferencing pointer to incomplete type
    put_device(&adev->dev);
                    ^


-- 
~Randy

      parent reply	other threads:[~2019-04-03 15:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03  8:24 linux-next: Tree for Apr 3 Stephen Rothwell
2019-04-03 15:02 ` linux-next: Tree for Apr 3 (objtool) Randy Dunlap
2019-04-03 20:53   ` Josh Poimboeuf
2019-04-03 22:29     ` Randy Dunlap
2019-04-04 17:16       ` Josh Poimboeuf
2019-04-04 20:51         ` Randy Dunlap
2019-04-05 20:53           ` Randy Dunlap
2019-04-03 15:20 ` 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=532f66c8-4c25-10d3-d119-71f3c8f82edd@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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
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).