From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>, Linux-MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 0/2] vfs: move the clone/dedupe/remap helpers to a single file
Date: Wed, 14 Oct 2020 19:48:25 -0700 [thread overview]
Message-ID: <CAHk-=wiXt28aJAoW_8gD=g1jvNaAE8NZ9M9eb7EknCJkzWc4qw@mail.gmail.com> (raw)
In-Reply-To: <160272187483.913987.4254237066433242737.stgit@magnolia>
On Wed, Oct 14, 2020 at 5:31 PM Darrick J. Wong <darrick.wong@oracle.com> wrote:
>
> So, I have a few questions, particularly for Al, Andrew, and Linus:
>
> (1) Do you find this reorganizing acceptable?
I don't see a problem.
> (3) Can I just grab the copyrights from mm/filemap.c? Or fs/read_write.c?
> Or something entirely different?
Heh. Those copyright notices look pretty old, and I'm not sure how
much - if anything - I had to do with the remap helpers.
I suspect just a
// SPDX-License-Identifier: GPL-2.0-only
is fine, with no need to try to drag along any other copyright notice
history from those two files.
Linus
next prev parent reply other threads:[~2020-10-15 2:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 0:31 [PATCH 0/2] vfs: move the clone/dedupe/remap helpers to a single file Darrick J. Wong
2020-10-15 0:31 ` [PATCH 1/2] vfs: move generic_remap_checks out of mm Darrick J. Wong
2020-10-15 11:38 ` Matthew Wilcox
2020-10-15 16:39 ` Darrick J. Wong
2020-10-15 0:31 ` [PATCH 2/2] vfs: move the remap range helpers to remap_range.c Darrick J. Wong
2020-10-15 2:48 ` Linus Torvalds [this message]
2020-10-15 3:18 ` [PATCH 0/2] vfs: move the clone/dedupe/remap helpers to a single file Al Viro
2020-10-15 16:46 ` Darrick J. Wong
2020-10-15 16:42 ` [PATCH 3/2] vfs: move the generic write and copy checks out of mm 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='CAHk-=wiXt28aJAoW_8gD=g1jvNaAE8NZ9M9eb7EknCJkzWc4qw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=darrick.wong@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
/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).