From: Pavel Machek <pavel@ucw.cz>
To: "Zhang, Rui" <rui.zhang@intel.com>
Cc: linux-acpi@vger.kernel.org, lenb@kernel.org, "Tian,
Kevin" <kevin.tian@intel.com>
Subject: Re: [PATCH]: ACPI: preserve the ebx value in acpi_copy_wakeup_routine
Date: Mon, 4 Jun 2007 12:37:06 +0200 [thread overview]
Message-ID: <20070604103706.GA4405@elf.ucw.cz> (raw)
In-Reply-To: <823A93EED437D048963A3697DB0E35DE16B6CB@pdsmsx414.ccr.corp.intel.com>
Hi!
> According to the SYSTEM V APPLICATION BINARY INTERFACE,
> Intel386 Architecture:
> "ecx and edx: Scratch registers have no specified role in the standard calling
> sequence. Functions do not have to preserve their values for the
> caller."
Thanks for confirming.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2007-06-04 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 10:09 [PATCH]: ACPI: preserve the ebx value in acpi_copy_wakeup_routine Zhang Rui
2007-06-01 10:17 ` Pavel Machek
2007-06-01 10:27 ` Zhang, Rui
2007-06-04 10:37 ` Pavel Machek [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=20070604103706.GA4405@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=kevin.tian@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@intel.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