From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Andrew Morton <akpm@osdl.org>
Cc: drzeus-list@drzeus.cx, linux-kernel@vger.kernel.org, ambx1@neo.rr.com
Subject: Re: [Fwd: [PATCH] [PNP][RFC] Suspend support for PNP bus.]
Date: Sun, 6 Nov 2005 11:50:44 -0500 [thread overview]
Message-ID: <200511061150.46007.dtor_core@ameritech.net> (raw)
In-Reply-To: <20051104231500.6a9272d1.akpm@osdl.org>
On Saturday 05 November 2005 02:15, Andrew Morton wrote:
> Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> >
> > On 11/4/05, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > >
> > > You lost me... We have a scenario when a PNP driver is bound to a PNP
> > > device that does not support deactivation. Looking at the proposed PNP
> > > bus suspend code presence of such device will cause suspend process to
> > > fail. Are you saying this is what you want?
> > >
> >
> > Ugh, scratch whatever I wrote earlier. Such devices should be marked
> > with RES_DO_NOT_CHANEG so everything is fine.
> >
> > Sorry about the noise.
>
> So... You're OK with the patch as proposed?
>
Yes I am.
--
Dmitry
next prev parent reply other threads:[~2005-11-06 16:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 9:21 [Fwd: [PATCH] [PNP][RFC] Suspend support for PNP bus.] Pierre Ossman
2005-11-04 14:49 ` Dmitry Torokhov
2005-11-04 15:16 ` Pierre Ossman
2005-11-04 15:27 ` Dmitry Torokhov
2005-11-04 15:52 ` Pierre Ossman
2005-11-04 16:09 ` Dmitry Torokhov
2005-11-04 16:12 ` Dmitry Torokhov
2005-11-05 7:15 ` Andrew Morton
2005-11-06 16:50 ` Dmitry Torokhov [this message]
2005-11-29 19:32 ` Andrew Morton
2005-11-29 18:50 ` Pierre Ossman
2005-11-29 20:02 ` Andrew Morton
2005-11-29 19:49 ` Pierre Ossman
2005-11-29 21:01 ` Andrew Morton
2005-11-29 20:44 ` Pierre Ossman
2005-11-30 10:12 ` Pierre Ossman
2005-11-30 10:44 ` Takashi Iwai
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=200511061150.46007.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=akpm@osdl.org \
--cc=ambx1@neo.rr.com \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
/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