From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] tracing/ftrace: don't trace on early stage of a secondary cpu boot
Date: Thu, 25 Dec 2008 10:56:37 +0100 [thread overview]
Message-ID: <20081225095637.GB28479@elte.hu> (raw)
In-Reply-To: <4952B7EA.8060100@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Thanks. Note that french people like me are silently cheating with the
> english language. We have a lot of similar words and we can survive
> while mumbling english, even with only few basis, but don't tell anyone,
> it's a secret ;-)
heh.
I guess it helps that more than half a millenium ago the fine folks on
those islands tried to learn French real hard [by virtue of being
conquered by the French] - and thus a healthy subset of the English
language (especially the more newfangled words) has thus become ... erm
... French? ;-)
Doh, i misspoke. What happened _really_ is that those friendly folks let
the French in as guests, and during that time of mutual understanding the
French learned and adopted half of the English language - greatly easing
communication today.
( And apparently there was some mingling with germanic tribes as well,
a few thousand years before that. Back then those germanic savages were
taught bits of proper English as well. )
( And then those folks forked their language into a "British" and "US"
versions. It is forwards compatible: if you speak British English then
by definition you can speak US English, but never the other way around.
US English was then taught to indian tribes - who, tens of thousands of
years ago, happened to have spoken the same language that the ancestors
of the germanic tribes spoke. [Or perhaps they spoke ancient Japanese -
memories are a bit fuzzy, records incomplete, and the issue is not fully
settled yet.] Anyway, it came around in a happy global circle and they
all speak English now! ;)
[ Except the celts, who insist that they were around even sooner than
that - starting in the happy times when you could walk on feet from
Scotland to Sweden with only a battle axe in your hand, when you
could slide stones weighing tons down an ice glacier and ship them to
flatland to build funny stone circles - and from whom everyone else
on this continent learned all the things worth learning. ]
> I applied your comments, see the patch below.
>
> From: Frederic Weisbecker <fweisbec@gmail.com>
> Subject: [PATCH v3] tracing/ftrace: don't trace on early stage of secondary cpu boot
applied to tip/tracing/ftrace, thanks Frederic!
Ingo
prev parent reply other threads:[~2008-12-25 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 14:48 Frederic Weisbecker
2008-12-24 15:15 ` Steven Rostedt
2008-12-24 22:30 ` Frederic Weisbecker
2008-12-25 9:56 ` Ingo Molnar [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=20081225095637.GB28479@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®