From: David Brownell <david-b@pacbell.net>
To: Dmitry Torokhov <dtor@insightbb.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>,
Alan Stern <stern@rowland.harvard.edu>, Greg KH <greg@kroah.com>,
LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH -mm 4/7] PM: Remove suspend and resume support from struct device_type
Date: Thu, 14 Jun 2007 07:19:28 -0700 [thread overview]
Message-ID: <200706140719.28829.david-b@pacbell.net> (raw)
In-Reply-To: <200706140010.03438.dtor@insightbb.com>
On Wednesday 13 June 2007, Dmitry Torokhov wrote:
> On Wednesday 13 June 2007 18:20, Kay Sievers wrote:
> > Dmitry, you added this recently, is this used in any code you plan to
> > merge soon?
> >
>
> Yes, I will need it to implement input device resume (mainly to restore LED
> state and repeat rate for keyboards).
Why wouldn't that use the class device suspend/resume mechanism?
next prev parent reply other threads:[~2007-06-14 14:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 13:51 [PATCH -mm 0/7] PM: Remove unused and unnecessary features from suspend and resume core Rafael J. Wysocki
2007-06-13 13:53 ` [PATCH -mm 1/7] PM: Remove pm_parent from struct dev_pm_info Rafael J. Wysocki
2007-06-13 13:55 ` [PATCH -mm 2/7] PM: Remove saved_state " Rafael J. Wysocki
2007-06-13 14:19 ` [PATCH -mm 3/7] PM: Simplify suspend_device Rafael J. Wysocki
2007-06-13 14:20 ` [PATCH -mm 4/7] PM: Remove suspend and resume support from struct device_type Rafael J. Wysocki
2007-06-13 22:20 ` Kay Sievers
2007-06-14 4:10 ` Dmitry Torokhov
2007-06-14 12:37 ` Rafael J. Wysocki
2007-06-14 12:59 ` Dmitry Torokhov
2007-06-14 17:46 ` Greg KH
2007-06-14 22:32 ` Rafael J. Wysocki
2007-06-14 22:50 ` Greg KH
2007-06-14 23:14 ` Greg KH
2007-06-14 23:30 ` Rafael J. Wysocki
2007-06-17 17:46 ` [PATCH -mm 0/3] PM: Remove unused and unnecessary features from core suspend code (continued) Rafael J. Wysocki
2007-06-17 17:48 ` [PATCH -mm 1/3] PM: Remove prev_state from struct dev_pm_info Rafael J. Wysocki
2007-06-17 17:49 ` [PATCH -mm 2/3] PM: Remove power_state.event checks from suspend core code Rafael J. Wysocki
2007-06-17 17:50 ` [PATCH -mm 3/3] PM: Do not check parent state in suspend and resume " Rafael J. Wysocki
2007-06-14 14:19 ` David Brownell [this message]
2007-06-14 14:44 ` [PATCH -mm 4/7] PM: Remove suspend and resume support from struct device_type Dmitry Torokhov
2007-06-14 15:03 ` David Brownell
2007-06-14 15:17 ` Dmitry Torokhov
2007-06-13 15:16 ` [PATCH -mm 5/7] PM: Remove prev_state from struct dev_pm_info Rafael J. Wysocki
2007-06-13 15:16 ` [PATCH -mm 6/7] PM: Remove power_state.event checks from suspend core code Rafael J. Wysocki
2007-06-14 14:21 ` David Brownell
2007-06-14 22:46 ` Rafael J. Wysocki
2007-06-15 2:00 ` Alan Stern
2007-06-15 21:57 ` Rafael J. Wysocki
2007-06-17 19:26 ` Rafael J. Wysocki
2007-06-13 15:17 ` [PATCH -mm 7/7] PM: Do not check parent state in suspend and resume " Rafael J. Wysocki
2007-06-13 21:59 ` [PATCH -mm 0/7] PM: Remove unused and unnecessary features from suspend and resume core Greg KH
2007-06-13 23:02 ` Rafael J. Wysocki
2007-06-13 23:36 ` Pavel Machek
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=200706140719.28829.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=dtor@insightbb.com \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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