Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp244445imm; Thu, 6 Sep 2018 01:34:40 -0700 (PDT) X-Google-Smtp-Source: ANB0VdbwOykwIG3vfJmTBO1t9tZ3AEDqzcuCy2FnyS/DBcSkllOgaEBAMSivtbspVlREdL/y62zx X-Received: by 2002:a63:c702:: with SMTP id n2-v6mr1709915pgg.108.1536222880881; Thu, 06 Sep 2018 01:34:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536222880; cv=none; d=google.com; s=arc-20160816; b=KTR8SHk431V78zuRzWgKUhHIcjLFC3rH9T6FnVoNIyME28Lf9pLs3DmrvB6R+CkDIO kEQB19F59QJr/GYympAm2/nkvenOSni8M0sg8ogf5DtpUJ9S7QzuWg6M8MY6V2vUf1ej O0oT/YvsHj423n1gSOSIEq2qXvBLU9rJpJikMJvUzELaYtg3EcEgZwvdBfKBPa0YMR13 dIxvuewbGmR749SuV/tQ3/8tbrMLFBCoMJdsVlwiVzyDsKPclbptLfIUAmPt+zL3Tafr XuPOegQtMZuIT2l4dC7ha203dwQiTHfUexec7LjA7I3eBHEh0aO4sl49VjIX+3QbeuTF HDrQ== 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; bh=4jBlSx0+6cd6V5qdfEHoowSo6dYjqsTjNbrGF6uS5gw=; b=I6oKiXoGdEoZIpKcKIOqkPsgHS2Y5gQcd7rtz5N2m6T/qAqJKLHHVrCRP0RgngXGT6 ynPVCYsTHgLvVW9Bp6cqfSMHoNfa1UengiH+MJ6uH1j/8sDXuMtyoStmiLeN+R2Qxm0Q PLk8noPyef7+2M0pQ6h3hoqJcl7LLx8fHVG8Q5G1Hn1LVnmu+FWo1EnDVYG/z9nrBrag o23ETyPHWWknTORH4CHAeMjRM+wp0bL4c7ezz/ZeWg/q/0qsgs/nhDcloZln1xYxqmKn DjUtQRFqR4rH9NeABCwctn9uz7dhsnD7SAhLLiXB3xh2jkplBqhSBSMxN5X24ZIf5YUm Gpqg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b34-v6si4421332pla.84.2018.09.06.01.34.25; Thu, 06 Sep 2018 01:34:40 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728133AbeIFNGM (ORCPT + 99 others); Thu, 6 Sep 2018 09:06:12 -0400 Received: from mx2.suse.de ([195.135.220.15]:38086 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725981AbeIFNGM (ORCPT ); Thu, 6 Sep 2018 09:06:12 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 69DC7AE02; Thu, 6 Sep 2018 08:31:51 +0000 (UTC) Date: Thu, 6 Sep 2018 10:31:49 +0200 From: Michal Hocko To: Mike Rapoport Cc: linux-mm@kvack.org, Andrew Morton , "David S. Miller" , Greg Kroah-Hartman , Ingo Molnar , Michael Ellerman , Paul Burton , Thomas Gleixner , Tony Luck , linux-ia64@vger.kernel.org, linux-mips@linux-mips.org, linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH 04/29] mm: remove bootmem allocator implementation. Message-ID: <20180906083149.GZ14951@dhcp22.suse.cz> References: <1536163184-26356-1-git-send-email-rppt@linux.vnet.ibm.com> <1536163184-26356-5-git-send-email-rppt@linux.vnet.ibm.com> <20180906073023.GO14951@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180906073023.GO14951@dhcp22.suse.cz> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 06-09-18 09:30:23, Michal Hocko wrote: > Is there any reason to keep > > ifdef CONFIG_NO_BOOTMEM > obj-y += nobootmem.o > else > obj-y += bootmem.o > endif > > behind? I can see you have done so in an earlier patch. I have missed that. -- Michal Hocko SUSE Labs