Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1385947 > unrolled thread
| Started by | Eric Engestrom <eric@engestrom.ch> |
|---|---|
| First post | 2016-04-25 02:30 +0200 |
| Last post | 2016-04-25 02:30 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
[PATCH 05/41] Documentation: cpu-hotplug: fix spelling mistake Eric Engestrom <eric@engestrom.ch> - 2016-04-25 02:30 +0200
| From | Eric Engestrom <eric@engestrom.ch> |
|---|---|
| Date | 2016-04-25 02:30 +0200 |
| Subject | [PATCH 05/41] Documentation: cpu-hotplug: fix spelling mistake |
| Message-ID | <rrCzw-4Wc-9@gated-at.bofh.it> |
Signed-off-by: Eric Engestrom <eric@engestrom.ch> --- Documentation/cpu-hotplug.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/cpu-hotplug.txt b/Documentation/cpu-hotplug.txt index dd68821..12e0b8f 100644 --- a/Documentation/cpu-hotplug.txt +++ b/Documentation/cpu-hotplug.txt @@ -97,7 +97,7 @@ from the map depending on the event is hot-add/hot-remove. There are currently no locking rules as of now. Typical usage is to init topology during boot, at which time hotplug is disabled. -You really dont need to manipulate any of the system cpu maps. They should +You really don't need to manipulate any of the system cpu maps. They should be read-only for most use. When setting up per-cpu resources almost always use cpu_possible_mask/for_each_possible_cpu() to iterate. -- 2.8.0
Back to top | Article view | linux.kernel
csiph-web