Return-Path: <linux-kernel-owner+w=401wt.eu-S1753500AbZCIN3Y@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753500AbZCIN3Y (ORCPT <rfc822;w@1wt.eu>);
	Mon, 9 Mar 2009 09:29:24 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751648AbZCIN0q
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 9 Mar 2009 09:26:46 -0400
Received: from cavan.codon.org.uk ([93.93.128.6]:47527 "EHLO
	vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751594AbZCIN0n (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 9 Mar 2009 09:26:43 -0400
Date: Mon, 9 Mar 2009 13:26:33 +0000
From: Matthew Garrett <mjg@redhat.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>, rjw@sisk.pl,
       hughsient@gmail.com, linux-acpi@vger.kernel.org,
       linux-kernel@vger.kernel.org
Subject: Re: suspend / hibernate nomenclature
Message-ID: <20090309132633.GB9797@srcf.ucam.org>
References: <1235992429.3858.58.camel@hughsie-work.lan> <15e53e180903080045x5874f05cv5ea836d73e3855b1@mail.gmail.com> <20090308144145.GB26233@srcf.ucam.org> <200903082156.46219.rjw@sisk.pl> <20090308230741.GA5357@dtor-d630.eng.vmware.com> <E1Lgatk-000Jyt-00.arvidjaar-mail-ru@mx5.mail.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1Lgatk-000Jyt-00.arvidjaar-mail-ru@mx5.mail.ru>
User-Agent: Mutt/1.5.12-2006-07-14
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: mjg59@codon.org.uk
X-SA-Exim-Scanned: No (on vavatch.codon.org.uk); SAEximRunCond expanded to false
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 874
Lines: 19

On Mon, Mar 09, 2009 at 11:31:36AM +0300, Andrey Borzenkov wrote:

> What about systems that have clear indication of STR and STD on respective 
> keys? Should they continue to return KEY_SLEEP for STR? I think this 
> conflicts with definition above. So in the long run those should be changed to 
> return KEY_SUSPEND2RAM it seems.

Perhaps, but at present they KEY_SLEEP is probably adequate. KEY_SLEEP 
is always going to default to suspend to RAM, so really the only 
distinction between it and a dedicated suspend to RAM key is whether a 
UI element affects its behaviour or not.

-- 
Matthew Garrett | mjg59@srcf.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/