From: Borislav Petkov <bp@alien8.de>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: perfbook@vger.kernel.org
Subject: Re: perfbook build error
Date: Thu, 11 Dec 2014 20:17:34 +0100 [thread overview]
Message-ID: <20141211191734.GG31140@pd.tnic> (raw)
In-Reply-To: <20141211190724.GF31140@pd.tnic>
Great, this moves the error to the next line:
---
diff --git a/toolsoftrade/toolsoftrade.tex b/toolsoftrade/toolsoftrade.tex
index c98f3a78652f..012f815fdd65 100644
--- a/toolsoftrade/toolsoftrade.tex
+++ b/toolsoftrade/toolsoftrade.tex
@@ -1242,8 +1242,8 @@ but may be implemented straightforwardly as follows:
\hline
\hline
Thread Management
- & \co{pthread_t}
- & \co{struct task_struct} \\
+ & pthread\_t
+ & struct task\_struct \\
\cline{2-3}
& \co{pthread_create()}
& \co{kthread_create} \\
--
so it can't stand the {}'s and the _'s all of a sudden.
Or my table format definition is screwed or so after the last update...
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-12-11 19:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141211173210.GE31140@pd.tnic>
2014-12-11 17:52 ` perfbook build error Paul E. McKenney
2014-12-11 19:07 ` Borislav Petkov
2014-12-11 19:17 ` Borislav Petkov [this message]
2014-12-11 19:32 ` Paul E. McKenney
2014-12-11 19:59 ` Borislav Petkov
2014-12-11 20:10 ` Paul E. McKenney
2014-12-11 20:22 ` Borislav Petkov
2014-12-11 21:14 ` Paul E. McKenney
2014-12-12 16:38 ` Paul E. McKenney
2014-12-12 17:53 ` Borislav Petkov
[not found] ` <20141212181804.GX25340@linux.vnet.ibm.com>
2014-12-12 18:47 ` Borislav Petkov
2014-12-12 18:58 ` Paul E. McKenney
2014-12-12 19:13 ` Borislav Petkov
2014-12-12 19:30 ` Paul E. McKenney
2014-12-12 20:15 ` Borislav Petkov
2014-12-12 20:27 ` Paul E. McKenney
2014-12-11 19:51 ` Paul E. McKenney
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=20141211191734.GG31140@pd.tnic \
--to=bp@alien8.de \
--cc=paulmck@linux.vnet.ibm.com \
--cc=perfbook@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.