Received: by 10.192.165.148 with SMTP id m20csp1917176imm; Thu, 26 Apr 2018 04:11:14 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/pOaWNuMVZDWcviKsCOhlQv+x6p5qIewOYqGccM+VamKgzddci6KtFt6am1zQ2RmVTxR5b X-Received: by 2002:a17:902:1aa:: with SMTP id b39-v6mr30232491plb.120.1524741074075; Thu, 26 Apr 2018 04:11:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524741074; cv=none; d=google.com; s=arc-20160816; b=eFIGs/TtoCIWkIzf7NHIbfTzLfNr5YdJaVLUZIChtT8UzUhpMS6rD3h4o5es9ap6Pz leTX1RpR9RXbXAe23XThb6FpKBTFQWLXz3UdaDJnBSdfLVRfa+ij9TQC8qlNDaHmy88O 7WF9JoY5omQFBCb6r+0xrtdHHN3KuKvnrAXpwd87ql5kRznOi9FJRbeLCmtFTpQ+JQAg uw5VKYj5sfrarqlmwuf211MRSZZSYfsNmywL7BiuQGS/A4rNtSxiooP7X+ni6ejW2Sbe UCHimFd0vrCS0SddQ8vy3HiaHsK07/ONT8D8DcJl1ANFtWtIBKXqJ2f1eKldZ20daIDt aPwA== 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-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=2DaXmv4t06EwcVAbA70Gv0Ugfq53F3TJsrWhAp80ePo=; b=iGO+ROKE51RXgzb/v4zluLCevCG04D7YyZvupKZivU0aUKvRbPXbUk58e/0ERA7crD qIL07BD0xL7biQ3nNSgLPMgnoxfvYdubNAFE694ff0T9ZzJ8duRYfirWmJjN2t1F3TTQ rzNzJ8VMjBTUIIxZpvooylxynhOv1XhUz1QSH5l8pLFZLGuve5QELFD4rPglMahGfxZt XQ+X9rZYDxIVaM333LSi358w2YQubSzaIRpWt2n0oV6sTw2flb/Uzm7tE6wEIbLzc2un KWq57Jd+3dizAUVFaWdDPwGqZPKwdzxV+Hhmm7XJClF81ZcpOGcM1lA5GziyoOk0ESkb QziA== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q14-v6si17778326pls.286.2018.04.26.04.10.59; Thu, 26 Apr 2018 04:11:14 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755314AbeDZLJV (ORCPT + 99 others); Thu, 26 Apr 2018 07:09:21 -0400 Received: from mx2.suse.de ([195.135.220.15]:50663 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755159AbeDZLJU (ORCPT ); Thu, 26 Apr 2018 07:09:20 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 5D198ACE5; Thu, 26 Apr 2018 11:09:19 +0000 (UTC) Date: Thu, 26 Apr 2018 13:09:05 +0200 From: Borislav Petkov To: Baoquan He Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org, robh+dt@kernel.org, dan.j.williams@intel.com, nicolas.pitre@linaro.org, josh@joshtriplett.org, Thomas Gleixner , Brijesh Singh , =?utf-8?B?SsOpcsO0bWU=?= Glisse , Tom Lendacky , Wei Yang Subject: Re: [PATCH v3 2/3] resource: add walk_system_ram_res_rev() Message-ID: <20180426110905.GH15043@pd.tnic> References: <20180419001848.3041-1-bhe@redhat.com> <20180419001848.3041-3-bhe@redhat.com> <20180419100745.GC3896@pd.tnic> <20180426085649.GC18395@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180426085649.GC18395@localhost.localdomain> User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 26, 2018 at 04:56:49PM +0800, Baoquan He wrote: > Sorry for that, I just ran scripts/get_maintainer.pl to get expert's > name and added them into each patch. The reason this change is made is > in patch 3/3. Test robot reported a code bug on the latest kernel, will > repost and CC everyone in all patches. > > > Rob Herring asked the same question in v2, I explained to him. The > discussion can be found here: > https://lkml.org/lkml/2018/4/10/484 ... and when I open that link, the first paragraph says: "This is the explanation I made when Andrew helped to review the v1 post: https://lkml.org/lkml/2018/3/23/78" Do you see the absurdity of the link chasing of your explanation?! Instead, the explanation *WHY* should be in the commit message of the patch - not in mail replies when people ask you about it. Also, do not use lkml.org when referencing a mail on lkml but use the Message-ID of the header. We have a proper redirector at https://lkml.kernel.org/r/ Now lemme read the reason finally... "We need unify these two interfaces on behaviour since they are the same on essense from the users' point of view... " That's not a good enough reason for me to cause code churn. If the only reason is: because the one does it top-down and the other bottom-up, I'm not convinced. -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --