From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 42B1D20352141 for ; Fri, 27 Apr 2018 01:37:04 -0700 (PDT) Received: by mail-pf0-x235.google.com with SMTP id j5so978405pfh.2 for ; Fri, 27 Apr 2018 01:37:04 -0700 (PDT) Date: Fri, 27 Apr 2018 01:37:02 -0700 (PDT) From: David Rientjes Subject: Re: [PATCH v3] dax: Change return type to vm_fault_t In-Reply-To: Message-ID: References: <20180417132842.GA30189@jordon-HP-15-Notebook-PC> MIME-Version: 1.0 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Souptick Joarder Cc: linux-nvdimm , Randy Dunlap , Matthew Wilcox , Andrew Morton List-ID: On Fri, 27 Apr 2018, Souptick Joarder wrote: > Hi Matthew/ Ross, > > There are two changes exist in mm/huge_memory.c as part of this > patch. vmf_insert_pfn_pmd() and vmf_insert_pfn_pud() functions are > invoked from this patch. > > Shall we put both in a single patch that it will easy to bisect in case > we have any issue ? > Please put them into a single patch, there's no reason to convert int foo() -> vm_fault_t foo() but leave int bar() { return foo() } It would be best just to convert all callers to also return vm_fault_t as I outlined in my response. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm