From: Peter Chen <peter.chen@freescale.com>
To: <jbaron@akamai.com>
Cc: <corbet@lwn.net>, <linux-kernel@vger.kernel.org>,
Peter Chen <peter.chen@freescale.com>, <stable@vger.kernel.org>
Subject: [PATCH 2/2] Doc: dynamic-debug-howto: fix the way to enable ddebug during boot process
Date: Tue, 27 Oct 2015 15:40:26 +0800 [thread overview]
Message-ID: <1445931626-11158-2-git-send-email-peter.chen@freescale.com> (raw)
In-Reply-To: <1445931626-11158-1-git-send-email-peter.chen@freescale.com>
Current non-module ddebug during boot process will fail due to
parse_args will delete space and give ddebug only the first
parameter, the code changes using comma to split ddebug parameters
for boot process, and we change documentation accordingly.
Signed-off-by: Peter Chen <peter.chen@freescale.com>
Cc: <stable@vger.kernel.org>
---
Documentation/dynamic-debug-howto.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/dynamic-debug-howto.txt b/Documentation/dynamic-debug-howto.txt
index 9417871..fcd9ca6 100644
--- a/Documentation/dynamic-debug-howto.txt
+++ b/Documentation/dynamic-debug-howto.txt
@@ -242,7 +242,7 @@ messages in all code run after this arch_initcall via this boot
parameter.
On an x86 system for example ACPI enablement is a subsys_initcall and
- dyndbg="file ec.c +p"
+ dyndbg="file,ec.c,+p"
will show early Embedded Controller transactions during ACPI setup if
your machine (typically a laptop) has an Embedded Controller.
PCI (or other devices) initialization also is a hot candidate for using
--
1.9.1
next prev parent reply other threads:[~2015-10-27 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 7:40 [PATCH 1/2] dynamic_debug: fix boot parameters parse Peter Chen
2015-10-27 7:40 ` Peter Chen [this message]
2015-10-28 14:17 ` Jason Baron
2015-10-29 6:22 ` Peter Chen
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=1445931626-11158-2-git-send-email-peter.chen@freescale.com \
--to=peter.chen@freescale.com \
--cc=corbet@lwn.net \
--cc=jbaron@akamai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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).