From: Andrey Erokhin <language.lawyer@gmail.com>
To: qemu-devel@nongnu.org
Cc: Christian Schoenebeck <qemu_oss@crudebyte.com>,
Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH v2] 9pfs: local: read native symlinks when security-model=mapped
Date: Tue, 25 Nov 2025 19:21:00 +0500 [thread overview]
Message-ID: <c9461c73-fbda-4963-b96c-3fd4b2d6ce41@gmail.com> (raw)
In-Reply-To: <20251125150444.5deb5195@bahia>
>> + native_symlink:;
>
> Still has the terminating but unneeded semicolon
I think I've addressed this in the v1 thread, with links to the C11 draft grammar.
Can repeat in plain English: a label shall be followed by a statement. (No, declaration is not a statement)
next prev parent reply other threads:[~2025-11-25 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-22 20:19 [PATCH v2] 9pfs: local: read native symlinks when security-model=mapped Andrey Erokhin
2025-11-25 14:04 ` Greg Kurz
2025-11-25 14:21 ` Andrey Erokhin [this message]
2025-11-25 18:58 ` Greg Kurz
2025-11-25 19:31 ` Christian Schoenebeck
2025-11-25 20:40 ` Andrey Erokhin
2025-11-26 12:26 ` Christian Schoenebeck
2025-11-28 10:23 ` Christian Schoenebeck
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=c9461c73-fbda-4963-b96c-3fd4b2d6ce41@gmail.com \
--to=language.lawyer@gmail.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
/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).