public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Couriousous <couriousous-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [PATCH] IASL disassembler bug with "Missing EndDependentFunctions" comment
Date: Sat, 3 Sep 2005 00:09:44 +0200	[thread overview]
Message-ID: <200509030009.44767.couriousous@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 469 bytes --]

Hello 

Sorry if it's the wrong list/email, but I didn't found a better one. There is 
no email on Intel website about the iasl disassembler.

When a dependent resource list doesn't end with EndDependentFn() macro, the 
iasl disassembler print the following comment in the disassembled source:

//*** Missing EndDependentFunctions descriptor

But it forget to terminate the comment by \n. So, the "next line" is on the 
same line as the comment.

Regards,
Couriousous 

[-- Attachment #2: EndDependentFunctions-comment-fix.patch --]
[-- Type: text/x-diff, Size: 499 bytes --]

--- disassembler/dmresrc.c.origi	2005-09-02 23:16:41.000000000 +0200
+++ disassembler/dmresrc.c	2005-09-02 23:17:12.000000000 +0200
@@ -303,7 +303,7 @@
                 AcpiOsPrintf ("}\n");
                 AcpiDmIndent (Level);
 
-                AcpiOsPrintf ("//*** Missing EndDependentFunctions descriptor");
+                AcpiOsPrintf ("//*** Missing EndDependentFunctions descriptor\n");
 
                 /*
                  * We could fix the problem, but then the ASL would not match

             reply	other threads:[~2005-09-02 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-02 22:09 Couriousous [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-02 22:20 [PATCH] IASL disassembler bug with "Missing EndDependentFunctions" comment Moore, Robert
     [not found] ` <971FCB6690CD0E4898387DBF7552B90E029D96D0-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-09-02 22:46   ` Couriousous
2005-09-02 22:48 Moore, Robert

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=200509030009.44767.couriousous@gmail.com \
    --to=couriousous-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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