From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 22800202BB9AE for ; Fri, 16 Aug 2019 14:03:23 -0700 (PDT) Date: Fri, 16 Aug 2019 14:01:34 -0700 From: Andrew Morton Subject: Re: [PATCH 1/4] resource: add a not device managed request_free_mem_region variant Message-Id: <20190816140134.1f3225bed9bf2734c03341b1@linux-foundation.org> In-Reply-To: <20190816065434.2129-2-hch@lst.de> References: <20190816065434.2129-1-hch@lst.de> <20190816065434.2129-2-hch@lst.de> Mime-Version: 1.0 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Christoph Hellwig Cc: linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org, Bharata B Rao , linux-mm@kvack.org, Jason Gunthorpe List-ID: On Fri, 16 Aug 2019 08:54:31 +0200 Christoph Hellwig wrote: > Just add a simple macro that passes a NULL dev argument to > dev_request_free_mem_region, and call request_mem_region in the > function for that particular case. Nit: > +struct resource *request_free_mem_region(struct resource *base, > + unsigned long size, const char *name); This isn't a macro ;) _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm