| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1461543878-3639-6-git-send-email-eric@engestrom.ch> Date: Mon, 25 Apr 2016 01:24:02 +0100 From: Eric Engestrom <eric@...estrom.ch> To: linux-kernel@...r.kernel.org Cc: Eric Engestrom <eric@...estrom.ch>, Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org Subject: [PATCH 05/41] Documentation: cpu-hotplug: fix spelling mistake Signed-off-by: Eric Engestrom <eric@...estrom.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
Powered by blists - more mailing lists