From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>,
linux-input@vger.kernel.org, maciej.rutecki@gmail.com,
alan-jenkins@tuffmail.co.uk, linux-kernel@vger.kernel.org,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] Input: mark serio and i8042 as suspended when hibernating too.
Date: Wed, 8 Jul 2009 13:06:55 +0200 [thread overview]
Message-ID: <200907081306.56804.rjw@sisk.pl> (raw)
In-Reply-To: <20090708065435.GF3309@dtor-d630.eng.vmware.com>
On Wednesday 08 July 2009, Dmitry Torokhov wrote:
> On Tue, Jul 07, 2009 at 12:40:42AM +0200, Rafael J. Wysocki wrote:
> > On Sunday 05 July 2009, Thadeu Lima de Souza Cascardo wrote:
> > > serio ports are not being restarted any longer because resume operations
> > > after hibernate do nothing, since the device has not been marked as
> > > suspended. This happens because suspend is only considering the SUSPEND
> > > event but not the FREEZE event.
> > >
> > > Note that this driver has still to migrate to dev_pm_ops, but this fixes
> > > this particular bug now.
> >
> > Hmm, this looks like a fix for:
> > http://bugzilla.kernel.org/show_bug.cgi?id=13643
> >
> > Any objections to merging it through the suspend tree?
> >
>
> Oops, just applied it to mine before reading your mail... I hope Linus
> will pick my pull request soon so it won't matter thoough.
No problem, I haven't added it to my for-linus branch yet.
Best,
Rafael
prev parent reply other threads:[~2009-07-08 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 2:13 [PATCH] Input: mark serio and i8042 as suspended when hibernating too Thadeu Lima de Souza Cascardo
2009-07-06 22:40 ` Rafael J. Wysocki
2009-07-06 23:33 ` Thadeu Lima de Souza Cascardo
2009-07-08 6:54 ` Dmitry Torokhov
2009-07-08 11:06 ` Rafael J. Wysocki [this message]
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=200907081306.56804.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=cascardo@holoscopio.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=maciej.rutecki@gmail.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).