From: "Moore, Robert" <robert.moore@intel.com>
To: "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>,
<acpi-devel@lists.sourceforge.net>
Cc: "Linux Kernel Mailinglist" <linux-kernel@vger.kernel.org>
Subject: RE: [ACPI] Re: [RFC] enhanced psxface.c error handling
Date: Thu, 4 Dec 2003 14:27:45 -0800 [thread overview]
Message-ID: <CFF522B18982EA4481D3A3E23B83141C24B5E7@orsmsx407.jf.intel.com> (raw)
I've made a stab at this in ACPI CA version 20031203. There are a
couple of additional subtleties to get unwound correctly with no memory
leaks.
It has turned into a bit of spaghetti code, I'm going to restructure it
later.
Bob
> -----Original Message-----
> From: acpi-devel-admin@lists.sourceforge.net [mailto:acpi-devel-
> admin@lists.sourceforge.net] On Behalf Of Felipe Alfaro Solana
> Sent: Thursday, December 04, 2003 2:00 PM
> To: acpi-devel@lists.sourceforge.net
> Cc: Linux Kernel Mailinglist
> Subject: [ACPI] Re: [RFC] enhanced psxface.c error handling
>
> On Thu, 2003-12-04 at 17:14, Mihai RUSU wrote:
>
> > I think you missed the order on this one
>
> Yep! You're right... thanks!
reply other threads:[~2003-12-04 22:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CFF522B18982EA4481D3A3E23B83141C24B5E7@orsmsx407.jf.intel.com \
--to=robert.moore@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=felipe_alfaro@linuxmail.org \
--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;
as well as URLs for NNTP newsgroup(s).