linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lv Zheng <lv.zheng@intel.com>
To: Robert Moore <robert.moore@intel.com>,
	Lv Zheng <lv.zheng@intel.com>,
	"David E. Box" <david.e.box@intel.com>,
	Borislav Petkov <bp@alien8.de>
Cc: Lv Zheng <zetalog@gmail.com>,
	linux-kernel@vger.kernel.org, devel@acpica.org,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <len.brown@intel.com>,
	linux-acpi@vger.kernel.org
Subject: [PATCH] acpiexec: Move an acpiexec specific purposed new line to acpiexec specific file
Date: Fri, 23 Sep 2016 14:49:26 +0800	[thread overview]
Message-ID: <1474613366-23043-1-git-send-email-lv.zheng@intel.com> (raw)
In-Reply-To: <20160919101234.r2zfor37m7eq6k6p@pd.tnic>

> No need, Robert did it already:
> 
> 1d435008fd9e ("Update an info message during table load phase.")

Not exactly what I meant. I meant the following on top of the above
mentioned commit. As the newline is an acpiexec specific logic, it should
be kept in acpiexec, shouldn't be left polluting a common file. Lv Zheng.

Signed-off-by: Lv Zheng <lv.zheng@intel.com>
--
Index: acpica/source/components/tables/tbxfload.c
===================================================================
--- acpica.orig/source/components/tables/tbxfload.c
+++ acpica/source/components/tables/tbxfload.c
@@ -348,11 +348,6 @@ AcpiTbLoadNamespace (
         Status = AE_CTRL_TERMINATE;
     }
 
-#ifdef ACPI_APPLICATION
-    ACPI_DEBUG_PRINT_RAW ((ACPI_DB_INIT, "\n"));
-#endif
-
-
 UnlockAndExit:
     (void) AcpiUtReleaseMutex (ACPI_MTX_TABLES);
     return_ACPI_STATUS (Status);
Index: acpica/source/tools/acpiexec/aetables.c
===================================================================
--- acpica.orig/source/tools/acpiexec/aetables.c
+++ acpica/source/tools/acpiexec/aetables.c
@@ -625,6 +625,7 @@ AeLoadTables (
 
     Status = AcpiLoadTables ();
     ACPI_CHECK_OK (AcpiLoadTables, Status);
+    ACPI_DEBUG_PRINT_RAW ((ACPI_DB_INIT, "\n"));
 
     /*
      * Test run-time control method installation. Do it twice to test code

      parent reply	other threads:[~2016-09-23  6:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 16:12 [PATCH] ACPICA / Interpreter: Remove redundant newline Borislav Petkov
2016-09-09 18:26 ` Moore, Robert
2016-09-09 18:40   ` Borislav Petkov
2016-09-09 18:46     ` Moore, Robert
2016-09-09 18:50       ` Borislav Petkov
2016-09-09 18:55     ` Joe Perches
2016-09-14  3:14       ` Zheng, Lv
2016-09-09 18:45   ` Moore, Robert
2016-09-09 19:06     ` Borislav Petkov
2016-09-09 19:15       ` Joe Perches
2016-09-09 19:25         ` Borislav Petkov
2016-09-14  3:11     ` Zheng, Lv
2016-09-14 14:03       ` Moore, Robert
2016-09-14  3:09 ` Zheng, Lv
2016-09-14 11:30   ` Borislav Petkov
2016-09-19  9:30     ` Zheng, Lv
2016-09-19 10:12       ` Borislav Petkov
2016-09-23  6:46         ` [PATCH] acpiexec: Move an acpiexec specific purposed new line to acpiexec specific file Lv Zheng
2016-09-23  6:49         ` Lv Zheng [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=1474613366-23043-1-git-send-email-lv.zheng@intel.com \
    --to=lv.zheng@intel.com \
    --cc=bp@alien8.de \
    --cc=david.e.box@intel.com \
    --cc=devel@acpica.org \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=robert.moore@intel.com \
    --cc=zetalog@gmail.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).