From: "J. Neuschäfer" <j.neuschaefer@9elements.com>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>,
"J. Neuschäfer" <j.neuschaefer@9elements.com>
Subject: [PATCH] docs/devel: Fix typo (s/exist paths/exit paths/)
Date: Wed, 20 May 2026 08:44:12 +0200 [thread overview]
Message-ID: <20260520-exist-v1-1-535f929a87ae@9elements.com> (raw)
In the discussion of control flow through a function, "exit paths" were meant.
Signed-off-by: J. Neuschäfer <j.neuschaefer@9elements.com>
---
docs/devel/style.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/devel/style.rst b/docs/devel/style.rst
index b8edcf9316f059fe15415543098118b28fcaf99c..f4da16a0e83ca6fed205e2516fff4ac2cc941d04 100644
--- a/docs/devel/style.rst
+++ b/docs/devel/style.rst
@@ -469,7 +469,7 @@ for a time/space trade-off like ``tlb_mmu_resize_locked`` in the
SoftMMU TLB code.
If the lifetime of the allocation is within the function and there are
-multiple exist paths you can also improve the readability of the code
+multiple exit paths you can also improve the readability of the code
by using ``g_autofree`` and related annotations. See :ref:`autofree-ref`
for more details.
---
base-commit: 6d17fd91f6cf88df5cb2205e578640d72605cc43
change-id: 20260520-exist-b23e143e9bfe
Best regards,
--
J. Neuschäfer <j.neuschaefer@9elements.com>
next reply other threads:[~2026-05-20 6:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 6:44 J. Neuschäfer [this message]
2026-05-20 7:54 ` [PATCH] docs/devel: Fix typo (s/exist paths/exit paths/) Daniel P. Berrangé
2026-05-20 12:14 ` Markus Armbruster
2026-05-22 18:06 ` Pierrick Bouvier
2026-05-25 15:23 ` Pierrick Bouvier
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=20260520-exist-v1-1-535f929a87ae@9elements.com \
--to=j.neuschaefer@9elements.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-devel@nongnu.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 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.