From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1753975Ab0AHUkP@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753975Ab0AHUkP (ORCPT <rfc822;w@1wt.eu>);
	Fri, 8 Jan 2010 15:40:15 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753928Ab0AHUkO
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Fri, 8 Jan 2010 15:40:14 -0500
Received: from vms173009pub.verizon.net ([206.46.173.9]:40864 "EHLO
	vms173009pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752289Ab0AHUkN (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 8 Jan 2010 15:40:13 -0500
Date: Fri, 08 Jan 2010 15:39:52 -0500 (EST)
From: Len Brown <lenb@kernel.org>
X-X-Sender: lenb@localhost.localdomain
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>, Matthew Garrett <mjg@redhat.com>,
       LKML <linux-kernel@vger.kernel.org>,
       pm list <linux-pm@lists.linux-foundation.org>,
       Alan Stern <stern@rowland.harvard.edu>,
       ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
       Linux PCI <linux-pci@vger.kernel.org>,
       Oliver Neukum <oliver@neukum.org>, Bjorn Helgaas <bjorn.helgaas@hp.com>,
       Shaohua Li <shaohua.li@intel.com>,
       Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: [PATCH 8/12] ACPI / PM: Add more run-time wake-up fields
In-reply-to: <200912272105.30352.rjw@sisk.pl>
Message-id: <alpine.LFD.2.00.1001081536100.4012@localhost.localdomain>
References: <200912272057.10443.rjw@sisk.pl> <200912272105.30352.rjw@sisk.pl>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

> Use the run_wake flag to mark all devices for which run-time wake-up
> events may be generated by the platform.  Introduce a new wake-up
> flag, special, for marking devices that should be permanently enabled
> to generate run-time events.

how about calling the flag "always_enabled" rather than "special"?

otherwise,
Acked-by: Len Brown <len.brown@intel.com>