From: Oliver Neukum <oneukum@suse.de>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: error returns of pm_runtime_get()
Date: Thu, 11 Sep 2014 15:27:06 +0200 [thread overview]
Message-ID: <1410442026.4966.8.camel@linux-fkkt.site> (raw)
In-Reply-To: <2871114.Byp9HpPsJ7@vostro.rjw.lan>
On Thu, 2014-09-11 at 02:03 +0200, Rafael J. Wysocki wrote:
> > The alternative is to make a conversion helper and to go through all
> > drivers. Not nice, but if necessary I'll do it.
>
> I honestly would prefer that.
Very well, then I shall do that.
Regards
Oliver
prev parent reply other threads:[~2014-09-11 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 12:43 error returns of pm_runtime_get() Oliver Neukum
2014-09-05 23:42 ` Rafael J. Wysocki
2014-09-10 13:04 ` Oliver Neukum
2014-09-11 0:03 ` Rafael J. Wysocki
2014-09-11 13:27 ` Oliver Neukum [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=1410442026.4966.8.camel@linux-fkkt.site \
--to=oneukum@suse.de \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--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;
as well as URLs for NNTP newsgroup(s).