From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 2252E1F461 for ; Mon, 8 Jul 2019 21:42:09 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:cc:subject:in-reply-to:date:message-id :mime-version:content-type; q=dns; s=default; b=tYd7QaqUJtTFF04m fIpnucVyutTzbIMpW88ZE1HYsiD+hqk5feQG+YlV+7Jrq8owNImseFECYEdy99Hb C+bkPdgU6oBCvtnJa5vd9WeBmsfuZtkeCNc08iCV4GHSVw9Cp6iE+P+ofZBntf1a PwLBaqSYeDKcSmfiGuGkdnWxj0s= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:cc:subject:in-reply-to:date:message-id :mime-version:content-type; s=default; bh=/r7/1Ngrc+zUv4ptPp57Mq 7mKXY=; b=ASB59jwUi4EOxNeKnU5GYiC7GD3CNe0PiXcErrm6j9qjVVmV9d0PJD jvvlatxnoksy4vfIZbhQYiPLepdt1xZ/COGMPedxgVEs9J1Z4dgsB+UM42AMFevx WhcoWQRMNShoveHB4zJam1FiecpczV1VigFjnsk4QiTmtGhfeJv2k= Received: (qmail 96574 invoked by alias); 8 Jul 2019 21:42:06 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 95562 invoked by uid 89); 8 Jul 2019 21:42:06 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: mx1.redhat.com From: DJ Delorie To: Florian Weimer Cc: libc-alpha@sourceware.org Subject: Re: [patch] NEWS: clarify copy_file_range In-Reply-To: <87zhlwdz1r.fsf@mid.deneb.enyo.de> (message from Florian Weimer on Tue, 02 Jul 2019 21:19:44 +0200) Date: Mon, 08 Jul 2019 17:41:58 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain >> 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 writes: > Looks good to me. Thanks. NP; pushed.