From: Mike Yuan <me@yhndnzj.com>
Date: Sat, 24 Feb 2024 05:26:19 +0000 (+0800)
Subject: docs/CODING_STYLE: fix typo (CLONE_VORK -> VFORK)
X-Git-Tag: v256-rc1~748
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3d3c42773d035ca261f4e64ad94f114cbd5fa0fb;p=thirdparty%2Fsystemd.git

docs/CODING_STYLE: fix typo (CLONE_VORK -> VFORK)
---

diff --git a/docs/CODING_STYLE.md b/docs/CODING_STYLE.md
index 0e761227348..6d6e549f5c7 100644
--- a/docs/CODING_STYLE.md
+++ b/docs/CODING_STYLE.md
@@ -774,7 +774,7 @@ SPDX-License-Identifier: LGPL-2.1-or-later
 - A corollary of the above is: never use `clone()` where a `fork()` would do
   too. Also consider using `posix_spawn()` which combines `clone()` +
   `execve()` into one and has nice properties since it avoids becoming a CoW
-  trap by using `CLONE_VORK` and `CLONE_VM` together.
+  trap by using `CLONE_VFORK` and `CLONE_VM` together.
 
 - While we avoid forking off threads on our own, writing thread-safe code is a
   good idea where it might end up running inside of libsystemd.so or