From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 894311310 for ; Fri, 5 Jul 2019 19:34:53 +0000 (UTC) Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0AAC387C for ; Fri, 5 Jul 2019 19:34:52 +0000 (UTC) Received: from pps.filterd (m0098414.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x65JWUi2013697 for ; Fri, 5 Jul 2019 15:34:52 -0400 Received: from e06smtp07.uk.ibm.com (e06smtp07.uk.ibm.com [195.75.94.103]) by mx0b-001b2d01.pphosted.com with ESMTP id 2tjb3h3rmq-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 05 Jul 2019 15:34:51 -0400 Received: from localhost by e06smtp07.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 5 Jul 2019 20:34:50 +0100 Date: Fri, 5 Jul 2019 22:34:44 +0300 From: Mike Rapoport To: Linus Walleij References: <37eb32f3-f341-b1d8-293b-c119ae278b4f@linuxfoundation.org> <1562082713.3321.38.camel@HansenPartnership.com> <201907020926.FB19EDEBCC@keescook> <1562103238.3321.66.camel@HansenPartnership.com> <1562106408.29304.11.camel@HansenPartnership.com> <20190702224347.GJ3032@mit.edu> <20190703085620.GA5007@pendragon.ideasonboard.com> <20190703135012.GC2041@mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Message-Id: <20190705193444.GB16150@rapoport-lnx> Cc: James Bottomley , ksummit-discuss@lists.linuxfoundation.org, Marek Szyprowski Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Patch version changes in commit logs? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, On Fri, Jul 05, 2019 at 11:26:22AM +0200, Linus Walleij wrote: > On Wed, Jul 3, 2019 at 3:51 PM Theodore Ts'o wrote: > > > Personally, if there is a case where it will be useful, it would > > actually be better for developers to summarize the comments, and > > design alternatives, considered and rejected, etc., in a cover letter, > > or better yet in the kernel documentation as part of the design doc > > for a largish feature, and then if it is a cover letter e-mailed out > > to the mailing list, include a link to the URL of the cover letter > > with some text so that a human being reading the commit log will know > > that there is something actually worth their time to read, as opposed > > to being treated to a huge amount of legislative history that, at the > > end of the day, be a complete waste of time to someone trying to debug > > a live production problem causing data outages for their company. > > I agree. I recently wanted to look into the development history > of the contiguous memory allocator merged in 2012. This patch set > went through 24 (!) iterations duly summarized in the cover letter: > https://lore.kernel.org/lkml/1333462221-3987-1-git-send-email-m.szyprowski@samsung.com/ > it not is on mm/cma.c. > > The links to the earlier iterations on gmane are dead. > > It is one of the more heroic attempts to fix a very real problem > with memory management in embedded and mobile, > the second part of which is hopefully coming to a resolution > with John Stultz work on the ION destaging (ongoing). > > The actual commit in the kernel looks like so: > git log c64be2bb1c6eb43c838b2c6d57b074078be208dd > > I would have to dig them all out of lore one by one to get > the picture (and I guess I will). The story of CMA is a really > interesting one, and now it is part of the MM core. > Documentation/cma is pretty empty. > > Asking Michal, Marek and Joonsoo who all worked hard on > this to summarize the development and make the design > and evolution of this feature understandable would be a > pretty big development task in itself so I'm not gonna. > > But maybe we should just merge a document with lore > pointers to Documentation/cma for this feature, and others > of the same impact? If you anyway going to dig through it, putting a summary with lore pointers in Documentation/ would be great. > Yours, > Linus Walleij > _______________________________________________ > Ksummit-discuss mailing list > Ksummit-discuss@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss > -- Sincerely yours, Mike.