linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: James Morris <jmorris@namei.org>
Cc: Len Brown <lenb@kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-pm@lists.linux-foundation.org, linux-acpi@vger.kernel.org,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Rajiv Andrade <srajiv@linux.vnet.ibm.com>
Subject: Re: [linux-pm] linux-next: Tree for May 6 (acpi: PM=n)
Date: Thu, 06 May 2010 16:38:57 -0700	[thread overview]
Message-ID: <4BE35311.7030502@oracle.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1005070910490.31779@tundra.namei.org>

On 05/06/10 16:27, James Morris wrote:
> On Thu, 6 May 2010, Randy Dunlap wrote:
> 
>> On Thu, 06 May 2010 16:26:13 -0400 (EDT) Len Brown wrote:
>>
>>>> When CONFIG_PM is not set:
>>>>
>>>> drivers/built-in.o: In function `acpi_init':
>>>> bus.c:(.init.text+0x2d84): undefined reference to `pm_flags'
>>>> bus.c:(.init.text+0x2d91): undefined reference to `pm_flags'
>>>
>>> CONFIG_ACPI depends on CONFIG_PM,
>>> so acpi/bus.c should not be compiled for CONFIG_PM=n
>>>
>>> Hmm, is is somebody doing something strange, like "select ACPI"
>>> without guaranteeing that all of ACPI's dependencies are satisfied?
>>
>> Oh, thanks for the clue.
>>
>> That would be a patch that I commented on and was ignored,
>> but James Morris merged it anyway.  Now it should be dropped.
>>
>> http://lkml.org/lkml/2010/5/4/379
> 
> You weren't ignored.  Mimi responded and mentioned a subsequent patch, 
> after which, there was no further discussion.

OK.  But merging a known bad patch doesn't make much sense to me.

> I've reverted:
> 
> b89e66e1e396f7b5436af154e58209320cc08aed
> "TPM: ACPI/PNP dependency removal"
> 
> a674fa46c79ffa37995bd1c8e4daa2b3be5a95ae
> "ima: remove ACPI dependency"
> 

Thanks.

> 
> Note: any further ACPI-related changes here should have acks from 
> linux-acpi folk.


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-05-06 23:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100506151502.f97afe54.sfr@canb.auug.org.au>
2010-05-06 15:05 ` linux-next: Tree for May 6 (acpi: PM=n) Randy Dunlap
2010-05-06 20:26   ` [linux-pm] " Len Brown
2010-05-06 20:32     ` Randy Dunlap
2010-05-06 23:27       ` James Morris
2010-05-06 23:38         ` Randy Dunlap [this message]
2010-05-06 15:07 ` linux-next: Tree for May 6 (acpi: PCI=n) Randy Dunlap
2010-05-06 20:29   ` Len Brown
2010-05-06 20:42     ` 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=4BE35311.7030502@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=jmorris@namei.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=sfr@canb.auug.org.au \
    --cc=srajiv@linux.vnet.ibm.com \
    --cc=zohar@linux.vnet.ibm.com \
    /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).