On 12/13/2011 11:04 AM, Rajaneesh Acharya wrote: > From cff3f3e6e389b146fdd06193ef9e7ca75f8b5b51 Mon Sep 17 00:00:00 2001 > From: Rajaneesh Acharya <rajaneesh.acharya@xxxxxxxxx> > Date: Tue, 13 Dec 2011 13:35:41 -0500 > Subject: [PATCH] The following are the enhancements that removed the errors while issuing "make pdfdocs" > > 1. Para nesting of para under the section kgdboc (moved the /para from line 210 to 202) > 2. Moved the paras under section 293 and 300 to section 3 > 3. Moved para block 358/361 outside nested para > > With these enhancement the pdf could be generated Hi Rajaneesh, In the future, please do not send linux kernel emails or patches in html format. No html at all. I managed to extract the patch from the reply text below, not from your original email. Jason, I can't get 'make pdfdocs' to work at all so I cannot verify that this patch is good. If you are OK with it, I can merge it. > --- > Documentation/DocBook/kgdb.tmpl | 6 +++--- > 1 files changed, 3 insertions(+), 3 deletions(-) > > diff --git a/Documentation/DocBook/kgdb.tmpl b/Documentation/DocBook/kgdb.tmpl > index d71b57f..d830bff 100644 > --- a/Documentation/DocBook/kgdb.tmpl > +++ b/Documentation/DocBook/kgdb.tmpl > @@ -199,6 +199,7 @@ > may be configured as a kernel built-in or a kernel loadable module. > You can only make use of <constant>kgdbwait</constant> and early > debugging if you build kgdboc into the kernel as a built-in. > + </para> > <para>Optionally you can elect to activate kms (Kernel Mode > Setting) integration. When you use kms with kgdboc and you have a > video driver that has atomic mode setting hooks, it is possible to > @@ -208,7 +209,6 @@ > crashes or doing analysis of memory with kdb while allowing the > full graphics console applications to run. > </para> > - </para> > <sect2 id="kgdbocArgs"> > <title>kgdboc arguments</title> > <para>Usage: <constant>kgdboc=[kms][[,]kbd][[,]serial_device][,baud]</constant></para> > @@ -289,7 +289,6 @@ > </listitem> > </orderedlist> > </para> > - </sect3> > <para>NOTE: Kgdboc does not support interrupting the target via the > gdb remote protocol. You must manually send a sysrq-g unless you > have a proxy that splits console output to a terminal program. > @@ -310,6 +309,7 @@ > as well as on the initial connect, or to use a debugger proxy that > allows an unmodified gdb to do the debugging. > </para> > + </sect3> > </sect2> > </sect1> > <sect1 id="kgdbwait"> > @@ -355,12 +355,12 @@ > </para> > </listitem> > </orderedlist> > + </para> > <para>IMPORTANT NOTE: You cannot use kgdboc + kgdbcon on a tty that is an > active system console. An example incorrect usage is <constant>console=ttyS0,115200 kgdboc=ttyS0 kgdbcon</constant> > </para> > <para>It is possible to use this option with kgdboc on a tty that is not a system console. > </para> > - </para> > </sect1> > </chapter> > <chapter id="usingKDB"> > -- -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
