From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot0-f200.google.com (mail-ot0-f200.google.com [74.125.82.200]) by kanga.kvack.org (Postfix) with ESMTP id 6FF746B06F9 for ; Sat, 12 May 2018 22:51:19 -0400 (EDT) Received: by mail-ot0-f200.google.com with SMTP id r104-v6so10866927ota.19 for ; Sat, 12 May 2018 19:51:19 -0700 (PDT) Received: from mail-sor-f41.google.com (mail-sor-f41.google.com. [209.85.220.41]) by mx.google.com with SMTPS id y12-v6sor3978875oie.16.2018.05.12.19.51.17 for (Google Transport Security); Sat, 12 May 2018 19:51:18 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20180512061712.GA26660@jordon-HP-15-Notebook-PC> <20180512142451.GB24215@bombadil.infradead.org> From: Dan Williams Date: Sat, 12 May 2018 19:51:17 -0700 Message-ID: Subject: Re: [PATCH v3] mm: Change return type to vm_fault_t Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Souptick Joarder Cc: Matthew Wilcox , Joe Perches , Andrew Morton , Michal Hocko , Hugh Dickins , David Rientjes , Mike Kravetz , Naoya Horiguchi , "Aneesh Kumar K.V" , Linux-MM , Linux Kernel Mailing List On Sat, May 12, 2018 at 12:14 PM, Souptick Joarder wrote: >>> It'd be nicer to realign the 2nd and 3rd arguments >>> on the subsequent lines. > >>> >>> vm_fault_t (*fault)(const struct vm_special_mapping *sm, >>> struct vm_area_struct *vma, >>> struct vm_fault *vmf); >>> >> > >> It'd be nicer if people didn't try to line up arguments at all and >> just indented by an extra two tabs when they had to break a logical >> line due to the 80-column limit. > > Matthew, there are two different opinions. Which one to take ? Unfortunately this is one of those "maintainer's choice" preferences that drives new contributors crazy. Just go with the two tabs like Matthew said and be done.