From: Theodore Ts'o <tytso@mit.edu>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: linux-ext4@vger.kernel.org, patches@groups.riscv.org
Subject: Re: [PATCH] Rename copy_file_range to _copy_file_range
Date: Thu, 28 Dec 2017 22:55:39 -0500 [thread overview]
Message-ID: <20171229035539.GB11757@thunk.org> (raw)
In-Reply-To: <20171229021828.5661-1-palmer@dabbelt.com>
On Thu, Dec 28, 2017 at 06:18:28PM -0800, Palmer Dabbelt wrote:
> As of 2.27, glibc will have a copy_file_range library call to wrap the
> new copy_file_range system call. This conflicts with the function in
> misc/create_inode.c, which this patch renames _copy_file_range.
Could you resend the patch renaming it to copy_file_chunk()? That's
less likely to cause confusion with the copy_file_range system call.
Thanks,
- Ted
next prev parent reply other threads:[~2017-12-29 3:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 2:18 [PATCH] Rename copy_file_range to _copy_file_range Palmer Dabbelt
2017-12-29 3:55 ` Theodore Ts'o [this message]
2017-12-29 18:19 ` [PATCH v2] Rename copy_file_range to copy_file_chunk Palmer Dabbelt
2018-01-02 4:41 ` Theodore Ts'o
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=20171229035539.GB11757@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=patches@groups.riscv.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 NNTP newsgroup(s).