From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752331AbcBYXM1 (ORCPT ); Thu, 25 Feb 2016 18:12:27 -0500 Received: from mail-pf0-f195.google.com ([209.85.192.195]:33602 "EHLO mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751849AbcBYXM0 (ORCPT ); Thu, 25 Feb 2016 18:12:26 -0500 From: SeongJae Park X-Google-Original-From: SeongJae Park Date: Fri, 26 Feb 2016 08:12:19 +0900 (KST) To: Chen Gang cc: Mel Gorman , trivial@kernel.org, akpm@linux-foundation.org, vbabka@suse.cz, rientjes@google.com, linux-kernel@vger.kernel.org, mhocko@suse.cz, hannes@cmpxchg.org, vdavydov@virtuozzo.com, dan.j.williams@intel.com, linux-mm@kvack.org, Chen Gang Subject: Re: [PATCH trivial] include/linux/gfp.h: Improve the coding styles In-Reply-To: <56CF8043.1030603@emindsoft.com.cn> Message-ID: References: <1456352791-2363-1-git-send-email-chengang@emindsoft.com.cn> <20160225092752.GU2854@techsingularity.net> <56CF1202.2020809@emindsoft.com.cn> <20160225160707.GX2854@techsingularity.net> <56CF8043.1030603@emindsoft.com.cn> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="781441777-1775379704-1456441944=:16296" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --781441777-1775379704-1456441944=:16296 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Fri, 26 Feb 2016, Chen Gang wrote: > On 2/26/16 00:07, Mel Gorman wrote: >>>> On Thu, Feb 25, 2016 at 06:26:31AM +0800, chengang@emindsoft.com.cn wrote: >> >> I do not want this patch to go through the trivial tree. It still adds >> another step to identifying relevant commits through git blame and has >> limited, if any, benefit to maintainability. >> >>> "it's preferable to preserve blame than go through a layer of cleanup >>> when looking for the commit that defined particular flags". >>> >> >> git blame identifies what commit last altered a line. If a cleanup patch >> is encountered then the tree before that commit needs to be examined >> which adds time. It's rare that cleanup patches on their own are useful >> and this is one of those cases. >> > > git is a tool mainly for analyzing code, but not mainly for normal > reading main code. > > So for me, the coding styles need not consider about git. It is common to see reject of trivial coding style fixup patch here and there. Those patches usually be merged for early stage files that only few people read / write. However, for files that are old and lots of people read and write, those patches are rejected in usual. I mean, the negative opinions for this patches are usual in this community. I agree that coding style is important and respect your effort. However, because the code will be seen and written by most kernel hackers, the file should be maintained to be easily readable and writable by most kernel hackers, especially, maintainers. What I want to say is, we should respect maintainers' opinion in usual. As far as I remember, I have seen a document that saying same with others' opinion but couldn't find it. Thanks, SeongJae Park > > > Thanks. > -- > Chen Gang (陈刚) > > Managing Natural Environments is the Duty of Human Beings. > > -- > To unsubscribe, send a message with 'unsubscribe linux-mm' in > the body to majordomo@kvack.org. For more info on Linux MM, > see: http://www.linux-mm.org/ . > Don't email: email@kvack.org > --781441777-1775379704-1456441944=:16296-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f181.google.com (mail-pf0-f181.google.com [209.85.192.181]) by kanga.kvack.org (Postfix) with ESMTP id F41556B0009 for ; Thu, 25 Feb 2016 18:12:26 -0500 (EST) Received: by mail-pf0-f181.google.com with SMTP id e127so40647043pfe.3 for ; Thu, 25 Feb 2016 15:12:26 -0800 (PST) Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com. [2607:f8b0:400e:c00::242]) by mx.google.com with ESMTPS id sm4si15256551pac.245.2016.02.25.15.12.26 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Feb 2016 15:12:26 -0800 (PST) Received: by mail-pf0-x242.google.com with SMTP id q63so325432pfb.1 for ; Thu, 25 Feb 2016 15:12:26 -0800 (PST) From: SeongJae Park Date: Fri, 26 Feb 2016 08:12:19 +0900 (KST) Subject: Re: [PATCH trivial] include/linux/gfp.h: Improve the coding styles In-Reply-To: <56CF8043.1030603@emindsoft.com.cn> Message-ID: References: <1456352791-2363-1-git-send-email-chengang@emindsoft.com.cn> <20160225092752.GU2854@techsingularity.net> <56CF1202.2020809@emindsoft.com.cn> <20160225160707.GX2854@techsingularity.net> <56CF8043.1030603@emindsoft.com.cn> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="781441777-1775379704-1456441944=:16296" Sender: owner-linux-mm@kvack.org List-ID: To: Chen Gang Cc: Mel Gorman , trivial@kernel.org, akpm@linux-foundation.org, vbabka@suse.cz, rientjes@google.com, linux-kernel@vger.kernel.org, mhocko@suse.cz, hannes@cmpxchg.org, vdavydov@virtuozzo.com, dan.j.williams@intel.com, linux-mm@kvack.org, Chen Gang This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --781441777-1775379704-1456441944=:16296 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Fri, 26 Feb 2016, Chen Gang wrote: > On 2/26/16 00:07, Mel Gorman wrote: >>>> On Thu, Feb 25, 2016 at 06:26:31AM +0800, chengang@emindsoft.com.cn wrote: >> >> I do not want this patch to go through the trivial tree. It still adds >> another step to identifying relevant commits through git blame and has >> limited, if any, benefit to maintainability. >> >>> "it's preferable to preserve blame than go through a layer of cleanup >>> when looking for the commit that defined particular flags". >>> >> >> git blame identifies what commit last altered a line. If a cleanup patch >> is encountered then the tree before that commit needs to be examined >> which adds time. It's rare that cleanup patches on their own are useful >> and this is one of those cases. >> > > git is a tool mainly for analyzing code, but not mainly for normal > reading main code. > > So for me, the coding styles need not consider about git. It is common to see reject of trivial coding style fixup patch here and there. Those patches usually be merged for early stage files that only few people read / write. However, for files that are old and lots of people read and write, those patches are rejected in usual. I mean, the negative opinions for this patches are usual in this community. I agree that coding style is important and respect your effort. However, because the code will be seen and written by most kernel hackers, the file should be maintained to be easily readable and writable by most kernel hackers, especially, maintainers. What I want to say is, we should respect maintainers' opinion in usual. As far as I remember, I have seen a document that saying same with others' opinion but couldn't find it. Thanks, SeongJae Park > > > Thanks. > -- > Chen Gang (e??a??) > > Managing Natural Environments is the Duty of Human Beings. > > -- > To unsubscribe, send a message with 'unsubscribe linux-mm' in > the body to majordomo@kvack.org. For more info on Linux MM, > see: http://www.linux-mm.org/ . > Don't email: email@kvack.org > --781441777-1775379704-1456441944=:16296-- -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org