Received: by 2002:a25:5b86:0:0:0:0:0 with SMTP id p128csp1329132ybb; Fri, 29 Mar 2019 02:14:40 -0700 (PDT) X-Google-Smtp-Source: APXvYqz4CM2QJnliFwKKEsA46EyiB3c4V6YTAa/KH1oWSvfW4im27ajMj5nxcIHejgkuh5WtCvAG X-Received: by 2002:a63:6985:: with SMTP id e127mr45248704pgc.101.1553850879841; Fri, 29 Mar 2019 02:14:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553850879; cv=none; d=google.com; s=arc-20160816; b=okNh+1hauC9nUTbYHvTz5PzB0qFFV2Nb1apycSGb66gF83L/12u55dtHaq4Ea/0EA4 gpfcuUSsVx1tzBk9aSMckFj8L3H1Luv+FXcUqxFV0GlxG7zGUyKuDtQQkzjXjY0crrdC 410Ywf2nJOHjFD63TrAWc8evccwtNSg6Rqf5bCW4ioXKM7GGl73SRqO8bzH7HMetR3e4 BHDM5DRBOUxLJh904W09AfMzlMS1WVT6FnsJu5wP5CshBLIk+tduYxZRi6z5CGYg6LvO sba1QMVKRd5/x4D/OyaFucKyfYCvKERGSYkDcGrvliiGjViIHHm6GPpVnGMJAt9iTw1D VnYA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=7dbCtRuPK+fGf8kjczUnXrEmzmPaf6kaofCaXTocWlg=; b=zhQySSCvFqWhRLfGt0YBmTFtK4Gl+0vIIgIoNpVDZyT3NVcjUEj4Y4jKFqA+upZgKJ Ej7KfV2qmd6Dliu2qEmdzVxEyV8eawK0tdgfVU9IYguuME8tPPOMqhTz8AT2qgtPTvnO V8pAGTl9+sZAssgr47mfHlqfRTj24qTx1/ATd7TSD7qzgUEdQkUQ2YP7m9kE0n2DBEab F27Uq+8CGifltTNHDkuWHKBvFfq6aC2tJjFehoahXcrbQyfvFqvUJ3Px7CKwxYIpuRxw 9M0HelKmDJWItfefuezYjcEn1nKyZMm81Fum/GVR0wrCcnM/NGkCXO9BILHE3ZPq4ImZ TqNw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g90si1565643plb.51.2019.03.29.02.14.24; Fri, 29 Mar 2019 02:14:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729249AbfC2JN2 (ORCPT + 99 others); Fri, 29 Mar 2019 05:13:28 -0400 Received: from mx2.suse.de ([195.135.220.15]:38610 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728703AbfC2JN1 (ORCPT ); Fri, 29 Mar 2019 05:13:27 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 89C11AE52; Fri, 29 Mar 2019 09:13:26 +0000 (UTC) Date: Fri, 29 Mar 2019 10:13:25 +0100 From: Michal Hocko To: Baoquan He Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, rafael@kernel.org, akpm@linux-foundation.org, osalvador@suse.de, rppt@linux.ibm.com, willy@infradead.org, fanc.fnst@cn.fujitsu.com Subject: Re: [PATCH v3 2/2] drivers/base/memory.c: Rename the misleading parameter Message-ID: <20190329091325.GD28616@dhcp22.suse.cz> References: <20190329082915.19763-1-bhe@redhat.com> <20190329082915.19763-2-bhe@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190329082915.19763-2-bhe@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 29-03-19 16:29:15, Baoquan He wrote: > The input parameter 'phys_index' of memory_block_action() is actually > the section number, but not the phys_index of memory_block. Fix it. I have tried to explain that the naming is mostly a relict from the past than really a misleading name http://lkml.kernel.org/r/20190326093315.GL28406@dhcp22.suse.cz Maybe it would be good to reflect that in the changelog > Signed-off-by: Baoquan He btw. I've acked the previous version as well. > --- > v2->v3: > Rename the parameter to 'start_section_nr' from 'sec'. > > drivers/base/memory.c | 7 ++++--- > 1 file changed, 4 insertions(+), 3 deletions(-) > > diff --git a/drivers/base/memory.c b/drivers/base/memory.c > index cb8347500ce2..9ea972b2ae79 100644 > --- a/drivers/base/memory.c > +++ b/drivers/base/memory.c > @@ -231,13 +231,14 @@ static bool pages_correctly_probed(unsigned long start_pfn) > * OK to have direct references to sparsemem variables in here. > */ > static int > -memory_block_action(unsigned long phys_index, unsigned long action, int online_type) > +memory_block_action(unsigned long start_section_nr, unsigned long action, > + int online_type) > { > unsigned long start_pfn; > unsigned long nr_pages = PAGES_PER_SECTION * sections_per_block; > int ret; > > - start_pfn = section_nr_to_pfn(phys_index); > + start_pfn = section_nr_to_pfn(start_section_nr); > > switch (action) { > case MEM_ONLINE: > @@ -251,7 +252,7 @@ memory_block_action(unsigned long phys_index, unsigned long action, int online_t > break; > default: > WARN(1, KERN_WARNING "%s(%ld, %ld) unknown action: " > - "%ld\n", __func__, phys_index, action, action); > + "%ld\n", __func__, start_section_nr, action, action); > ret = -EINVAL; > } > > -- > 2.17.2 > -- Michal Hocko SUSE Labs