[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20161121222829.30e2bf67c58af5f1c91d1a1b@linux-foundation.org>
Date: Mon, 21 Nov 2016 22:28:29 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Alexander Duyck <alexander.duyck@...il.com>
Cc: Alexander Duyck <alexander.h.duyck@...el.com>,
linux-mm <linux-mm@...ck.org>, Netdev <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [mm PATCH v3 21/23] mm: Add support for releasing multiple
instances of a page
On Mon, 21 Nov 2016 08:21:39 -0800 Alexander Duyck <alexander.duyck@...il.com> wrote:
> >> + __free_pages_ok(page, order);
> >> + }
> >> +}
> >> +EXPORT_SYMBOL(__page_frag_drain);
> >
> > It's an exported-to-modules library function. It should be documented,
> > please? The page-frag API is only partially documented, but that's no
> > excuse.
>
> Okay. I assume you want the documentation as a follow-up patch since
> I received a notice that the patch was added to -mm?
Yes please. Or a replacement patch which I'll temporarily turn into a
delta, either is fine.
> If you would like I could look at doing a couple of renaming patches
> so that we make the API a bit more consistent. I could move the
> __alloc and __free to what you have suggested, and then take a look at
> trying to rename the refill/drain to be a bit more consistent in terms
> of what they are supposed to work on and how they are supposed to be
> used.
I think that would be better - it's hardly high-priority but a bit of
attention to the documentation and naming conventions would help tidy
things up. When you can't find anything else to do ;)
Powered by blists - more mailing lists