Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3457683imm; Tue, 29 May 2018 07:35:49 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoMZKVLzrRN8L6IkCscgn/EKK448ZwoMj5x8aZ4q2NrIu3qvG+7H1dD0XMDlPUslDv311+P X-Received: by 2002:a62:9fca:: with SMTP id v71-v6mr17607547pfk.233.1527604549646; Tue, 29 May 2018 07:35:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527604549; cv=none; d=google.com; s=arc-20160816; b=0uiBOzsfVfmAkLIMW9KtpMaZ+mI6d6E2pfqCMk6WPoMDOwmmeAzh07F3HWILYGi2dX +Zrlq4NvSwxVXlUwXOd3sSxap2PrHnRtwFeDeEjdust4UlsxrObskGLpUA900Hl1VwQH iRAteLwjhGgcyurCOZpnnDyIMI/xrwvBi4FUQEbnF3A9fXnOD5bOECT+vZOo9DXk5IU/ H4JWQB+KOq8sQcqifYwKx/0jKSgW7MJe2fMrUovdLYln3V6DC3O88Edu8rQT0g9mtyG0 rGaNRIejr/VTU59sccDtkvtw8jbSfPK7kVcomX3cGO42nr0XaJSo83huKVVWTBl9mJkT zdRQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=UlKEwUCzPfsryJK6HlmtD48uzoVZbF8Rf6ScOPOszKU=; b=eHbn1rMkHXZomNMU18uV9Agk1G40y2rPQRWdEGNZjtd7w+fdZmwjVuzRwiTB3/Gzc0 RKmqiaWDsuls4Y3vpEXxb8i7v/lxIAi3ApG2pHfkMlDtBvXMbk8/CXUYHqwJKnzdx6Kh BjhLpzCBchui4ya+arXc2VX/VFaSLprcN2b7L2cZeqWAvnjCiuqLYL9w2lyXEW5lu3iw RmwZynYKfSjo/cUF76hdqW3ZplnLXOChKBMUnAElegMza15MVbh/0ekBwsy2zhTY9hQM mxijCJpGSekSRo0vMhI9GxcYnVfYRdg3H8+qzSxSjqwzissPcIJl0UCQzII4Vm5UbF00 gaLQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=qXyXdJ6O; 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=pass (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 s4-v6si25879617pgn.403.2018.05.29.07.35.35; Tue, 29 May 2018 07:35:49 -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; dkim=pass header.i=@kernel.org header.s=default header.b=qXyXdJ6O; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934867AbeE2Oe4 (ORCPT + 99 others); Tue, 29 May 2018 10:34:56 -0400 Received: from mail.kernel.org ([198.145.29.99]:54522 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934608AbeE2Oez (ORCPT ); Tue, 29 May 2018 10:34:55 -0400 Received: from mail-qk0-f176.google.com (mail-qk0-f176.google.com [209.85.220.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id CBE93208A1; Tue, 29 May 2018 14:34:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1527604495; bh=uZU2jg8OMzkr0gw2UNaUHHo2GbJEezWkXqZf6iB8yCE=; h=In-Reply-To:References:From:Date:Subject:To:Cc:From; b=qXyXdJ6OKFcn22gx2PpJozvpxmQgXFuTmE628B8o5xV9P10iDbI4mowly4us7sozb 7GjRUztsUXKLfH94uPjciNw1VVoGNAosbrKT2F2LnETfxVsCrmUvAqWXb09pJanWzQ 6UTFXjOjJnkx7j+20UC7qsulH70EbFSODO7tiJ8M= Received: by mail-qk0-f176.google.com with SMTP id d130-v6so6227708qkc.2; Tue, 29 May 2018 07:34:54 -0700 (PDT) X-Gm-Message-State: ALKqPwd7hfGkr67cGjRMn1Ok3tlPP10QxGls9gcAaK3aSGK2HhtPEAve o6lngbhhAQAwiet6twvMoAIICEskw7Zj+OgxMQ== X-Received: by 2002:a37:bbc3:: with SMTP id l186-v6mr14965035qkf.120.1527604493997; Tue, 29 May 2018 07:34:53 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a0c:9b02:0:0:0:0:0 with HTTP; Tue, 29 May 2018 07:34:33 -0700 (PDT) In-Reply-To: <20180528100058.705378203@linuxfoundation.org> References: <20180528100050.700971285@linuxfoundation.org> <20180528100058.705378203@linuxfoundation.org> From: Rob Herring Date: Tue, 29 May 2018 09:34:33 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 3.18 093/185] microblaze: switch to NO_BOOTMEM To: Greg Kroah-Hartman Cc: "linux-kernel@vger.kernel.org" , stable , Alvaro Gamez Machado , Michal Simek , Sasha Levin Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 28, 2018 at 5:02 AM, Greg Kroah-Hartman wrote: > 3.18-stable review patch. If anyone has any objections, please let me know. > > ------------------ > > From: Rob Herring > > [ Upstream commit 101646a24a2f9cdb61d7732459fbf068a7bbb542 ] > > Microblaze doesn't set CONFIG_NO_BOOTMEM and so memblock_virt_alloc() > doesn't work for CONFIG_HAVE_MEMBLOCK && !CONFIG_NO_BOOTMEM. Unless Michal feels differently, I don't think this should go in stable. The DT change that broke microblaze is only in 4.16 . Rob