From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 1/3] linux: Move flockfile/_IO_flockfile into libc
Date: Fri, 07 May 2021 08:37:59 +0200 [thread overview]
Message-ID: <87wnsbf3qw.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <42041e57-3761-885f-c109-6c0da7bc5c44@linaro.org> (Adhemerval Zanella's message of "Thu, 6 May 2021 18:01:04 -0300")
* Adhemerval Zanella:
> I tried to just mimic what is currently done, but if you prefer we can
> always use the libpthread version as default.
Yes, please.
> For _IO_FLAGS2_NEED_LOCK set, I think we should set only when get the
> stream lock.
Probably, but let's keep that as a separate change.
Thanks,
Florian
prev parent reply other threads:[~2021-05-07 6:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 20:06 Adhemerval Zanella
2021-05-06 20:06 ` [PATCH 2/3] linux: Move ftrylockfile/_IO_ftrylockfile " Adhemerval Zanella
2021-05-06 20:06 ` [PATCH 3/3] linux: Move funlockfile/_IO_funlockfile " Adhemerval Zanella
2021-05-06 20:34 ` [PATCH 1/3] linux: Move flockfile/_IO_flockfile " Florian Weimer
2021-05-06 21:01 ` Adhemerval Zanella
2021-05-07 6:37 ` Florian Weimer [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=87wnsbf3qw.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).