All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Al Stone <al.stone@linaro.org>
Cc: linaro-kernel@lists.linaro.org, linux-acpi@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Hanjun Guo <hanjun.guo@linaro.org>,
	patches@linaro.org, linaro-acpi@lists.linaro.org
Subject: Re: [PATCH] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE_ONLY to enforce this ACPI mode
Date: Fri, 17 Jan 2014 16:10:02 +0100	[thread overview]
Message-ID: <201401171610.02887.arnd@arndb.de> (raw)
In-Reply-To: <52D82671.6000200@linaro.org>

On Thursday 16 January 2014, Al Stone wrote:
> Right; I assumed I had to have that SELECT.  My apologies -- I
> still cannot reproduce the warning.  I'll resubmit the patch
> incorporating the suggestion, though, since the result ends up
> being the same -- you must have ACPI and EXPERT selected in order
> to enable ACPI_REDUCED_HARDWARE_ONLY.
> 

You should never 'select' CONFIG_EXPERT from architecture code, that
is supposed to be a user-settable option. If you also select CONFIG_EXPERT
or have that enabled in the configuration, you will not get a warning.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE_ONLY to enforce this ACPI mode
Date: Fri, 17 Jan 2014 16:10:02 +0100	[thread overview]
Message-ID: <201401171610.02887.arnd@arndb.de> (raw)
In-Reply-To: <52D82671.6000200@linaro.org>

On Thursday 16 January 2014, Al Stone wrote:
> Right; I assumed I had to have that SELECT.  My apologies -- I
> still cannot reproduce the warning.  I'll resubmit the patch
> incorporating the suggestion, though, since the result ends up
> being the same -- you must have ACPI and EXPERT selected in order
> to enable ACPI_REDUCED_HARDWARE_ONLY.
> 

You should never 'select' CONFIG_EXPERT from architecture code, that
is supposed to be a user-settable option. If you also select CONFIG_EXPERT
or have that enabled in the configuration, you will not get a warning.

	Arnd

  reply	other threads:[~2014-01-17 15:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 20:37 [PATCH] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE_ONLY to enforce this ACPI mode al.stone
2014-01-14 20:37 ` al.stone at linaro.org
2014-01-14 21:26 ` Arnd Bergmann
2014-01-14 21:26   ` Arnd Bergmann
2014-01-16  2:17   ` Al Stone
2014-01-16  2:17     ` Al Stone
2014-01-16 10:55     ` Arnd Bergmann
2014-01-16 10:55       ` Arnd Bergmann
2014-01-16 18:35       ` Al Stone
2014-01-16 18:35         ` Al Stone
2014-01-17 15:10         ` Arnd Bergmann [this message]
2014-01-17 15:10           ` Arnd Bergmann

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=201401171610.02887.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=al.stone@linaro.org \
    --cc=hanjun.guo@linaro.org \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=patches@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.