From: DJ Delorie <dj@redhat.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: libc-alpha@sourceware.org
Subject: Re: [patch] NEWS: clarify copy_file_range
Date: Mon, 08 Jul 2019 17:41:58 -0400 [thread overview]
Message-ID: <xnzhloqk49.fsf@greed.delorie.com> (raw)
In-Reply-To: <87zhlwdz1r.fsf@mid.deneb.enyo.de> (message from Florian Weimer on Tue, 02 Jul 2019 21:19:44 +0200)
>> diff --git a/NEWS b/NEWS
>> index 6c7de105ac..11099f7248 100644
>> --- a/NEWS
>> +++ b/NEWS
>> @@ -46,9 +46,11 @@ Deprecated and removed features, and other changes affecting compatibility:
>> support the system call of the same name. Previously, user space
>> emulation was performed, but its behavior did not match the kernel
>> behavior, which was deemed too confusing. Applications which use the
>> - copy_file_range function will have to be run on kernels which implement
>> - the copy_file_range system call. Support for most architectures was added
>> - in version 4.5 of the mainline Linux kernel.
>> + copy_file_range function can no longer rely on glibc to provide a fallback
>> + on kernels that do not support the copy_file_range system call, and if
>> + this function returns ENOSYS, they will need to use their own fallback.
>> + Support for copy_file_range for most architectures was added in version
>> + 4.5 of the mainline Linux kernel.
Florian Weimer <fw@deneb.enyo.de> writes:
> Looks good to me. Thanks.
NP; pushed.
prev parent reply other threads:[~2019-07-08 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 19:17 [patch] NEWS: clarify copy_file_range DJ Delorie
2019-07-02 19:19 ` Florian Weimer
2019-07-08 21:41 ` DJ Delorie [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xnzhloqk49.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=fw@deneb.enyo.de \
--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).