From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christoph Hellwig <hch@lst.de>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Jason Gunthorpe" <jgg@mellanox.com>,
"Christoph Hellwig" <hch@infradead.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Thomas Hellström" <thomas@shipmail.org>,
"Jerome Glisse" <jglisse@redhat.com>,
"Steven Price" <steven.price@arm.com>,
Linux-MM <linux-mm@kvack.org>,
"Linux List Kernel Mailing" <linux-kernel@vger.kernel.org>,
"Minchan Kim" <minchan@kernel.org>
Subject: Re: cleanup the walk_page_range interface
Date: Sat, 17 Aug 2019 16:58:33 +1000 [thread overview]
Message-ID: <20190817165833.369c943c@canb.auug.org.au> (raw)
In-Reply-To: <20190817064301.GA18544@lst.de>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
Hi Christoph,
On Sat, 17 Aug 2019 08:43:01 +0200 Christoph Hellwig <hch@lst.de> wrote:
>
> On Sat, Aug 17, 2019 at 04:41:24PM +1000, Stephen Rothwell wrote:
> > I certainly prefer that method of API change :-)
> > (see the current "keys: Replace uid/gid/perm permissions checking with
> > an ACL" in linux-next and the (currently) three merge fixup patches I
> > am carrying. Its not bad when people provide the fixes, but I am no
> > expert in most areas of the kernel ...)
>
> It would mean pretty much duplicating all the code. And then never
> finish the migration because new users of the old interfaces keep
> popping up. Compared to that I'd much much prefer either Linus
> taking it now or a branch.
Sure, I have no problem with either of these two choices, or, at least,
hints/resolutions when conflicts are expected. My time (each day) is
already getting pretty short since we are almost up to -rc5 ...
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-17 6:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 15:42 cleanup the walk_page_range interface Christoph Hellwig
2019-08-08 15:42 ` [PATCH 1/3] mm: split out a new pagewalk.h header from mm.h Christoph Hellwig
2019-08-08 15:42 ` [PATCH 2/3] pagewalk: seperate function pointers from iterator data Christoph Hellwig
2019-08-08 20:34 ` Thomas Hellstrom
2019-08-09 8:57 ` Steven Price
2019-08-08 15:42 ` [PATCH 3/3] pagewalk: use lockdep_assert_held for locking validation Christoph Hellwig
2019-08-08 18:18 ` Matthew Wilcox
2019-08-08 17:50 ` cleanup the walk_page_range interface Linus Torvalds
2019-08-08 21:56 ` Christoph Hellwig
2019-08-08 22:21 ` Thomas Hellstrom
2019-08-09 14:36 ` Christoph Hellwig
2019-08-12 6:17 ` Mike Rapoport
2019-08-16 6:27 ` Christoph Hellwig
2019-08-16 11:57 ` Jason Gunthorpe
2019-08-16 12:32 ` Christoph Hellwig
2019-08-16 16:20 ` Linus Torvalds
2019-08-16 21:06 ` Andrew Morton
2019-08-17 6:41 ` Stephen Rothwell
2019-08-17 6:43 ` Christoph Hellwig
2019-08-17 6:58 ` Stephen Rothwell [this message]
2019-08-17 7:37 ` Linus Torvalds
2019-08-23 13:43 ` Jason Gunthorpe
2019-08-23 15:36 ` Steven Price
2019-08-24 22:26 ` Christoph Hellwig
2019-08-27 1:34 ` Jason Gunthorpe
2019-08-27 23:34 ` Andrew Morton
2019-08-27 23:36 ` Jason Gunthorpe
2019-08-28 6:20 ` Christoph Hellwig
2019-08-28 13:23 ` Steven Price
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=20190817165833.369c943c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=jgg@mellanox.com \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=steven.price@arm.com \
--cc=thomas@shipmail.org \
--cc=torvalds@linux-foundation.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).