From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Cc: "Dr. David Alan Gilbert" <dave@treblig.org>
Subject: [PATCH] documentation: local_ops fix on_each_cpu
Date: Mon, 1 Dec 2008 05:46:38 -0500 [thread overview]
Message-ID: <20081201104638.GD25340@Krystal> (raw)
* Dr. David Alan Gilbert (dave@treblig.org) wrote:
[...]
> I noticed while looking at something else that the example in
> local_ops.txt still has the 4 operand on_each_cpu in the latest git;
> I don't know the rest of the code around there very well so I thought
> it best to mention it rather than post a patch.
Reported-by: Dr. David Alan Gilbert <dave@treblig.org>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
CC: Ingo Molnar <mingo@elte.hu>
---
Documentation/local_ops.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6-lttng/Documentation/local_ops.txt
===================================================================
--- linux-2.6-lttng.orig/Documentation/local_ops.txt 2008-12-01 05:29:25.000000000 -0500
+++ linux-2.6-lttng/Documentation/local_ops.txt 2008-12-01 05:29:49.000000000 -0500
@@ -149,7 +149,7 @@ static void do_test_timer(unsigned long
int cpu;
/* Increment the counters */
- on_each_cpu(test_each, NULL, 0, 1);
+ on_each_cpu(test_each, NULL, 1);
/* Read all the counters */
printk("Counters read from CPU %d\n", smp_processor_id());
for_each_online_cpu(cpu) {
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next reply other threads:[~2008-12-01 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 10:46 Mathieu Desnoyers [this message]
2008-12-01 12:51 ` [PATCH] documentation: local_ops fix on_each_cpu Ingo Molnar
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=20081201104638.GD25340@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=dave@treblig.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.