From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Yann Droneaud <ydroneaud@opteya.com>,
libc-alpha@sourceware.org, Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH v5 5/8] linux: Add fspick
Date: Fri, 10 Jun 2022 14:19:18 -0300 [thread overview]
Message-ID: <b6f173fd-40d2-2a87-b2d4-aae32579edc9@linaro.org> (raw)
In-Reply-To: <421dadf5-fc31-a062-4426-32dc75640b4c@opteya.com>
On 07/06/2022 13:19, Yann Droneaud wrote:
>> /* The type of fsconfig call made. */
>> enum fsconfig_command
>> {
>> @@ -219,6 +227,10 @@ extern int move_mount (int __from_dfd, const char *__from_pathname,
>> extern int fsconfig (int __fd, unsigned int __cmd, const char *__key,
>> const char *__value, int __aux) __THROW;
>> +/* Equivalent of fopen for for an existing mount point. */
>
>
> Equivalent of fsopen for an existing mount point
Ack, fixed.
next prev parent reply other threads:[~2022-06-10 17:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 13:44 [PATCH v5 0/8] linux: Add new syscalls Adhemerval Zanella
2022-06-06 13:44 ` [PATCH v5 1/8] linux: Add fsopen Adhemerval Zanella
2022-06-17 21:28 ` Carlos O'Donell
2022-06-22 12:30 ` Adhemerval Zanella
2022-06-06 13:44 ` [PATCH v5 2/8] linux: Add fsmount Adhemerval Zanella
2022-06-07 16:14 ` Yann Droneaud
2022-06-10 17:16 ` Adhemerval Zanella
2022-06-18 6:15 ` Carlos O'Donell
2022-06-22 12:41 ` Adhemerval Zanella
2022-06-06 13:44 ` [PATCH v5 3/8] linux: Add move_mount Adhemerval Zanella
2022-06-06 13:44 ` [PATCH v5 4/8] linux: Add fsconfig Adhemerval Zanella
2022-06-06 13:44 ` [PATCH v5 5/8] linux: Add fspick Adhemerval Zanella
2022-06-07 16:19 ` Yann Droneaud
2022-06-10 17:19 ` Adhemerval Zanella [this message]
2022-06-06 13:44 ` [PATCH v5 6/8] linux: Add open_tree Adhemerval Zanella
2022-06-06 13:44 ` [PATCH v5 7/8] linux: Add tst-mount to check for Linux new mount API Adhemerval Zanella
2022-06-06 13:44 ` [PATCH v5 8/8] linux: Add mount_setattr Adhemerval Zanella
2022-06-07 16:27 ` Yann Droneaud
2022-06-10 17:21 ` Adhemerval Zanella
2022-06-07 16:34 ` Yann Droneaud
2022-06-07 18:10 ` Christian Brauner
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=b6f173fd-40d2-2a87-b2d4-aae32579edc9@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=ydroneaud@opteya.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 read-only IMAP folder(s) and NNTP newsgroup(s).