From: Richard Henderson <richard.henderson@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 46/48] qom: remove return after g_assert_not_reached()
Date: Thu, 12 Sep 2024 11:20:44 -0700 [thread overview]
Message-ID: <dc9390db-0128-4d52-85da-f960d835c05f@linaro.org> (raw)
In-Reply-To: <20240912161150.483515-3-pierrick.bouvier@linaro.org>
On 9/12/24 09:11, Pierrick Bouvier wrote:
> This patch is part of a series that moves towards a consistent use of
> g_assert_not_reached() rather than an ad hoc mix of different
> assertion mechanisms.
>
> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
> ---
> qom/object.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/qom/object.c b/qom/object.c
> index 157a45c5f8b..28c5b66eab5 100644
> --- a/qom/object.c
> +++ b/qom/object.c
> @@ -2079,7 +2079,6 @@ const char *object_get_canonical_path_component(const Object *obj)
>
> /* obj had a parent but was not a child, should never happen */
> g_assert_not_reached();
> - return NULL;
> }
>
> char *object_get_canonical_path(const Object *obj)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2024-09-12 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 16:11 [PATCH v2 44/48] migration: remove return after g_assert_not_reached() Pierrick Bouvier
2024-09-12 16:11 ` [PATCH v2 45/48] qobject: " Pierrick Bouvier
2024-09-12 18:20 ` Richard Henderson
2024-09-12 16:11 ` [PATCH v2 46/48] qom: " Pierrick Bouvier
2024-09-12 18:20 ` Richard Henderson [this message]
2024-09-12 16:11 ` [PATCH v2 47/48] tests/qtest: " Pierrick Bouvier
2024-09-12 18:21 ` Richard Henderson
2024-09-12 16:11 ` [PATCH v2 48/48] scripts/checkpatch.pl: emit error when using assert(false) Pierrick Bouvier
2024-09-12 18:19 ` [PATCH v2 44/48] migration: remove return after g_assert_not_reached() Richard Henderson
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=dc9390db-0128-4d52-85da-f960d835c05f@linaro.org \
--to=richard.henderson@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).