From: Paul Mackerras <paulus@samba.org>
To: Haren Myneni <haren@us.ibm.com>
Cc: External List <linuxppc-dev@ozlabs.org>,
Nathan Lynch <ntl@pobox.com>, Milton Miller <miltonm@bga.com>
Subject: Re: [PATCH] Add rtas_set_indicator_fast() for RTAS call without extended delay
Date: Mon, 31 Jul 2006 14:04:21 +1000 [thread overview]
Message-ID: <17613.33093.767856.432771@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <44C9301C.7080300@us.ibm.com>
Haren Myneni writes:
> + WARN_ON(rc == -2 || (rc >= 9900 && rc <= 9905));
This worries me... do we know for sure that RTAS will never return a
busy code? If it could possibly return a busy code, and we can't
sleep, then we should spin doing the call again and again until it
works, I think.
Paul.
next prev parent reply other threads:[~2006-07-31 4:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 4:52 [PATCH] Add rtas_set_indicator_fast() for RTAS call without extended delay Haren Myneni
2006-07-26 22:04 ` Nathan Lynch
2006-07-27 21:29 ` Haren Myneni
2006-07-31 4:04 ` Paul Mackerras [this message]
2006-07-31 4:38 ` Nathan Lynch
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=17613.33093.767856.432771@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=haren@us.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--cc=ntl@pobox.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).