From: Richard Henderson <richard.henderson@linaro.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Will Cohen <wwcohen@gmail.com>, Greg Kurz <groug@kaod.org>,
Akihiko Odaki <akihiko.odaki@gmail.com>
Subject: Re: [PULL 0/7] 9p queue 2022-04-30
Date: Sat, 30 Apr 2022 13:16:56 -0700 [thread overview]
Message-ID: <1d8dfad2-c183-8113-f09c-bd5d9c33722e@linaro.org> (raw)
In-Reply-To: <3704033.BMyLRrx2Jx@silver>
On 4/30/22 12:29, Christian Schoenebeck wrote:
> I suggest I just s/AT_SYMLINK_NOFOLLOW_ANY/AT_SYMLINK_NOFOLLOW/ on my end and
> post v2 PR, for consistency and as it does not really make a huge difference
> IMO which one of the two is used in create_socket_file_at_cwd().
>
> Any objections?
Sounds good.
r~
prev parent reply other threads:[~2022-04-30 20:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 11:44 [PULL 0/7] 9p queue 2022-04-30 Christian Schoenebeck
2022-04-30 11:44 ` [PULL 6/7] 9pfs: fix removing non-existent POSIX ACL xattr on macOS host Christian Schoenebeck
2022-04-30 11:44 ` [PULL 2/7] 9pfs: fix qemu_mknodat(S_IFREG) on macOS Christian Schoenebeck
2022-04-30 11:44 ` [PULL 7/7] 9pfs: fix qemu_mknodat() to always return -1 on error on macOS host Christian Schoenebeck
2022-04-30 11:44 ` [PULL 1/7] 9pfs: fix inode sequencing in 'synth' driver Christian Schoenebeck
2022-04-30 11:44 ` [PULL 3/7] 9pfs: fix qemu_mknodat(S_IFSOCK) on macOS Christian Schoenebeck
2022-04-30 11:44 ` [PULL 5/7] 9pfs: fix wrong errno being sent to Linux client on macOS host Christian Schoenebeck
2022-04-30 11:44 ` [PULL 4/7] 9pfs: fix wrong encoding of rdev field in Rgetattr on macOS Christian Schoenebeck
2022-04-30 16:37 ` [PULL 0/7] 9p queue 2022-04-30 Richard Henderson
2022-04-30 19:29 ` Christian Schoenebeck
2022-04-30 20:16 ` Richard Henderson [this message]
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=1d8dfad2-c183-8113-f09c-bd5d9c33722e@linaro.org \
--to=richard.henderson@linaro.org \
--cc=akihiko.odaki@gmail.com \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--cc=wwcohen@gmail.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).