From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
Adam Belay <ambx1@neo.rr.com>
Subject: Re: [Fwd: [PATCH] [PNP][RFC] Suspend support for PNP bus.]
Date: Fri, 4 Nov 2005 09:49:30 -0500 [thread overview]
Message-ID: <d120d5000511040649u5b33405an73b5e33fb4ce5cf6@mail.gmail.com> (raw)
In-Reply-To: <436B2819.4090909@drzeus.cx>
On 11/4/05, Pierre Ossman <drzeus-list@drzeus.cx> wrote:
> +
> +int pnp_start_dev(struct pnp_dev *dev)
> +{
> + if (!pnp_can_write(dev)) {
> + pnp_info("Device %s does not supported activation.", dev->dev.bus_id);
"...does not support...", there is no "ed" at the end.
> + return -EINVAL;
> + }
Hmm, would'nt presence of such device stop suspend process? It will
cause pnp_bus_resume to fail too. Perhaps returning 0 in this case is
better.
> +
> +int pnp_stop_dev(struct pnp_dev *dev)
> +{
> + if (!pnp_can_disable(dev)) {
> + pnp_info("Device %s does not supported disabling.", dev->dev.bus_id);
> + return -EINVAL;
Same here. No "ed" and -EINVAL will hurt.
--
Dmitry
next prev parent reply other threads:[~2005-11-04 14:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 9:21 Pierre Ossman
2005-11-04 14:49 ` Dmitry Torokhov [this message]
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
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=d120d5000511040649u5b33405an73b5e33fb4ce5cf6@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@osdl.org \
--cc=ambx1@neo.rr.com \
--cc=drzeus-list@drzeus.cx \
--cc=dtor_core@ameritech.net \
--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
all inboxes | Powered by JetHome®