Received: by 10.192.165.148 with SMTP id m20csp942522imm; Fri, 27 Apr 2018 09:57:00 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoKeIwXgkYhyubEGnzKdcgZEkWyGq6ATR21UuSInYTfe9niV880eMHfZjk3BMK7hDSRzCXL X-Received: by 2002:a63:6f82:: with SMTP id k124-v6mr2661871pgc.301.1524848220341; Fri, 27 Apr 2018 09:57:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524848220; cv=none; d=google.com; s=arc-20160816; b=Wttjt9ROX4BUa3lMziN85TFZEGQrFJ3TTwIckbzA/lkWyFRAVGUTufFFeQ2DLeX6xM T7mEQjh+uNBsnF+DW8IK5QKuEVs9YpoQx2z0U6/lUcEI2B5thXcIhvS+sBXD2+WhgznD wJfUqNcmc/Hgvo1iC5lfDHbvKAGOp8xbY3h1id6IzD0bEifix1JJ3qNz6SwjSwq1AbN6 WK0VYY6fuKPuJDnrGUivbqpnZ1TJgcDaJ8uZDE2lWUFr+rF59gEznbq8EchB5Hzk+g9H yEom3GZpvt9MO+VZtPz49j1T1fr3tjPVjzjRWYxaTlMSKromKufo+jeOBhpxhyaIFMWL cqPg== 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-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=CGgTq+vZxdomB0SJBALnskG1quGb+EiQ7Zz+IbGGhrA=; b=QszXQy4hE4Jtt09LxuxrrB8tmbKZOKXfE6jeBtkmeARDu5DzmwEMNiWKcxdPwPufk6 6FlrhPT9tJY9q0UPazXvsZ0q/UB/ULsgYSVy9/CHg7t6GqLTDLCigoJypUVJBRn2k87/ d5+FsNpyKcl4y7+Qjrm+jlrBHQ6h2jBWYdwIDOz6l/XLiikOt8EqiAAuhPpzXPg3xYGN VSSc9I587JdUhrUFMr6BpbgkIVMnqvuHj4Q5+J2ALxGzj3U/0nmfuZgPeotOJEGv7wRT N/wgxC8kvE7bunmmI3duqfjUfUXBtpKxEaJq6wntkvi7J+iv9E/Ks1UabCWHAvlN1jQA zlTA== 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 203si1497842pfz.160.2018.04.27.09.56.46; Fri, 27 Apr 2018 09:57:00 -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 S1758792AbeD0Qze (ORCPT + 99 others); Fri, 27 Apr 2018 12:55:34 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:43758 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757569AbeD0Qzd (ORCPT ); Fri, 27 Apr 2018 12:55:33 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 504B815AD; Fri, 27 Apr 2018 09:55:33 -0700 (PDT) Received: from edgewater-inn.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 20EB03F4FF; Fri, 27 Apr 2018 09:55:33 -0700 (PDT) Received: by edgewater-inn.cambridge.arm.com (Postfix, from userid 1000) id 308721AE523C; Fri, 27 Apr 2018 17:55:53 +0100 (BST) Date: Fri, 27 Apr 2018 17:55:53 +0100 From: Will Deacon To: Chandan Vn Cc: Laura Abbott , CHANDAN VN , catalin.marinas@arm.com, Takahiro Akashi , james.morse@arm.com, robin.murphy@arm.com, steve.capper@arm.com, kristina.martsenko@arm.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, cpgs@samsung.com Subject: Re: [PATCH 1/1] arm64: To remove initrd reserved area entry from memblock Message-ID: <20180427165552.GC5286@arm.com> References: <1522990390-30804-1-git-send-email-chandan.vn@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 23, 2018 at 10:30:49AM +0530, Chandan Vn wrote: > May I know when this patch would be taken for merging? Please can you send a new version, stating in the commit message that this only affects accountinga and debugging, rather than plugging an actual memory leak? Cheers, Will