Thread (47 messages) 47 messages, 5 authors, 2019-11-05

Re: [PATCH 02/19] mm/gup: factor out duplicate code from four routines

From: John Hubbard <jhubbard@nvidia.com>
Date: 2019-10-31 22:01:20
Also in: bpf, dri-devel, kvm, linux-block, linux-doc, linux-fsdevel, linux-kselftest, linux-media, linux-mm, linux-rdma, linuxppc-dev, lkml

On 10/31/19 2:09 PM, Ira Weiny wrote:
On Thu, Oct 31, 2019 at 11:43:37AM -0700, John Hubbard wrote:
quoted
On 10/31/19 11:35 AM, Ira Weiny wrote:
quoted
On Wed, Oct 30, 2019 at 03:49:13PM -0700, John Hubbard wrote:
...
quoted
quoted
+
+static int __huge_pt_done(struct page *head, int nr_recorded_pages, int *nr)
+{
+	*nr += nr_recorded_pages;
+	SetPageReferenced(head);
+	return 1;
When will this return anything but 1?
Never, but it saves a line at all four call sites, by having it return like that.

I could see how maybe people would prefer to just have it be a void function,
and return 1 directly at the call sites. Since this was a lower line count I
thought maybe it would be slightly better, but it's hard to say really.
It is a NIT perhaps but I feel like the signature of a function should stand on
it's own.  What this does is mix the meaning of this function with those
calling it.  Which IMO is not good style.

We can see what others say.
Sure. I'll plan on changing it to a void return type, then, unless someone else
pipes up.


thanks,

John Hubbard
NVIDIA
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help