public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-man@vger.kernel.org, Amir Goldstein <amir73il@gmail.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Luis Henriques <lhenriques@suse.de>,
	Steve French <sfrench@samba.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Anna Schumaker <anna.schumaker@netapp.com>,
	Jeff Layton <jlayton@kernel.org>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Trond Myklebust <trond.myklebust@hammerspace.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	Dave Chinner <dchinner@redhat.com>,
	Nicolas Boichat <drinkcat@chromium.org>,
	Ian Lance Taylor <iant@google.com>,
	Luis Lozano <llozano@chromium.org>,
	Andreas Dilger <adilger@dilger.ca>,
	Olga Kornievskaia <aglo@umich.edu>,
	Christoph Hellwig <hch@infradead.org>,
	ceph-devel <ceph-devel@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	CIFS <linux-cifs@vger.kernel.org>,
	samba-technical <samba-technical@lists.samba.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Walter Harms <wharms@bfs.de>
Subject: Re: [RFC v4] copy_file_range.2: Update cross-filesystem support for 5.12
Date: Thu, 4 Mar 2021 19:24:02 +0100	[thread overview]
Message-ID: <37df00f9-a88e-3f16-d0b4-3297248aee66@gmail.com> (raw)
In-Reply-To: <20210304171350.GC7267@magnolia>

Hi Darrick,

On 3/4/21 6:13 PM, Darrick J. Wong wrote:
> On Thu, Mar 04, 2021 at 10:38:07AM +0100, Alejandro Colomar wrote:
>> +However, on some virtual filesystems,
>> +the call failed to copy, while still reporting success.
> 
> ...success, or merely a short copy?

Okay.

> 
> (The rest looks reasonable (at least by c_f_r standards) to me.)

I'm curious, what does "c_f_r standards" mean? :)

Cheers,

Alex

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-03-04 18:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210222102456.6692-1-lhenriques@suse.de>
2021-02-24 14:23 ` [PATCH] copy_file_range.2: Kernel v5.12 updates Luis Henriques
2021-02-24 16:10   ` Amir Goldstein
2021-02-25 10:21     ` Luis Henriques
2021-02-25 15:29       ` AW: " Walter Harms
2021-02-26 10:13       ` Alejandro Colomar (man-pages)
2021-02-26 10:34         ` Amir Goldstein
2021-02-26 11:15           ` Alejandro Colomar (man-pages)
2021-02-26 13:59             ` Jeff Layton
2021-02-26 21:26               ` Alejandro Colomar (man-pages)
2021-02-26 22:18     ` Alejandro Colomar (man-pages)
2021-02-27  5:41       ` Amir Goldstein
2021-02-27 12:20         ` Alejandro Colomar (man-pages)
2021-02-27 13:49           ` [RFC v2] copy_file_range.2: Update cross-filesystem support for 5.12 Alejandro Colomar
2021-02-27 16:00             ` Amir Goldstein
2021-02-27 23:08         ` [PATCH] copy_file_range.2: Kernel v5.12 updates Steve French
2021-02-28  7:35           ` Amir Goldstein
2021-02-28 22:25             ` Steve French
2021-03-01  6:18               ` Amir Goldstein
2021-03-01 14:41   ` [RFC v3] copy_file_range.2: Update cross-filesystem support for 5.12 Alejandro Colomar
2021-03-01 14:58     ` Amir Goldstein
2021-03-04  9:38   ` [RFC v4] " Alejandro Colomar
2021-03-04 17:13     ` Darrick J. Wong
2021-03-04 18:24       ` Alejandro Colomar (man-pages) [this message]
2021-03-04 23:50         ` Darrick J. Wong

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=37df00f9-a88e-3f16-d0b4-3297248aee66@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=adilger@dilger.ca \
    --cc=aglo@umich.edu \
    --cc=amir73il@gmail.com \
    --cc=anna.schumaker@netapp.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=darrick.wong@oracle.com \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=drinkcat@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=iant@google.com \
    --cc=jlayton@kernel.org \
    --cc=lhenriques@suse.de \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=llozano@chromium.org \
    --cc=miklos@szeredi.hu \
    --cc=mtk.manpages@gmail.com \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.org \
    --cc=trond.myklebust@hammerspace.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wharms@bfs.de \
    /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