From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Florian Weimer <fweimer@redhat.com>, <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Fix Linux fcntl OFD locks for non-LFS architectures (BZ#20251)
Date: Fri, 01 Jun 2018 20:50:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1806012049040.25633@digraph.polyomino.org.uk> (raw)
In-Reply-To: <b4364cd6-0416-0665-aafb-09345b3f00af@linaro.org>
On Fri, 1 Jun 2018, Adhemerval Zanella wrote:
> It is not really new, since for architectures with default LFS support this is
> transparent and for architectures with non-default LFS my understanding is
> functions with *64 suffix are expected to handle cancellation as the non-LFS.
*64 functions are generally expected to be analogous with the
corresponding non-LFS functions, yes. I think the new fcntl64 API still
merits a specific NEWS entry, just like other new function APIs.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-06-01 20:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 21:27 Adhemerval Zanella
2018-04-30 11:10 ` Adhemerval Zanella
2018-05-04 17:54 ` Adhemerval Zanella
2018-05-21 19:01 ` Adhemerval Zanella
2018-05-25 20:03 ` Adhemerval Zanella
2018-06-01 14:49 ` Adhemerval Zanella
2018-06-01 15:00 ` Florian Weimer
2018-06-01 20:38 ` Adhemerval Zanella
2018-06-01 20:50 ` Joseph Myers [this message]
2018-06-01 21:49 ` Adhemerval Zanella
2018-06-01 21:07 ` Florian Weimer
2018-06-01 21:48 ` Adhemerval Zanella
2018-06-01 21:53 ` Adhemerval Zanella
2018-06-02 8:00 ` Florian Weimer
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=alpine.DEB.2.20.1806012049040.25633@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--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).