From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AC481C433F5 for ; Thu, 30 Sep 2021 21:26:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8F77D61A63 for ; Thu, 30 Sep 2021 21:26:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229999AbhI3V16 (ORCPT ); Thu, 30 Sep 2021 17:27:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48174 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229992AbhI3V15 (ORCPT ); Thu, 30 Sep 2021 17:27:57 -0400 Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 89694C06176A for ; Thu, 30 Sep 2021 14:26:14 -0700 (PDT) Received: by mail-ot1-x32c.google.com with SMTP id d12-20020a05683025cc00b0054d8486c6b8so9131665otu.0 for ; Thu, 30 Sep 2021 14:26:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=h/TBKn03dF9IntMFcuDE9WlvX4rnNMcxTnYaxfj4f3M=; b=BlxMYaM/OWq2QOg73mmSIuZReJqS9WDVJwYpygBxYlCdpjQvMPkG8JUUJuWMEfe7VW Kc4xJOkMskHk8O+awxj6C0zYig/iRuEgT85zngr4j5VHau1O2THU+xT3x/AlUo4/mD7V wX52wLkXcsoyoK8aKbnCd70Ljj6pEqXvKGjjk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=h/TBKn03dF9IntMFcuDE9WlvX4rnNMcxTnYaxfj4f3M=; b=zRKGtDj5V7miQGXA4/Bxa2oIjnE6w2bytEdCvrd5SHEGrZd/bsIb40QMaRoPSRwLhW p+BpfPvr0A5fvSWlb7cHNNkreh7LkI53QwqauzAp0IUs0nAYPjqHImBNH9nDK63uNCVL yL3+2hTQgrf+434Oxd5QK72g0kLFZBK86355aE7SbZe8AZeOMQLXFD/ZamQzRWTYqG/E fIWHeV/vcqUsR18EHgBSeYiAaA4k7D9pJuB4efiSkdYt7lyLnEVhszSV/CqzNEP6fxic 6gvtZI0snnCucDEk56ssKFS5qAUc4u+09smKWyPV2O4gHF4aWbyVWjICyO4lSYt7i4ko 9w9w== X-Gm-Message-State: AOAM530/wXrvJAoB8FJ4BIOH4Gsg1Gj3m5ECP4JWvPXjMgXWDWMwEr+o hVxTc/iXDJeVJ9edGiZKbvriUk3XA+hpEGTPH2M= X-Google-Smtp-Source: ABdhPJyC+4CArXUh4u+urscbjdSEkN0MwfJCJx7TTEue1ISqr2xUJPL1pMGKW8z3SJt1qFVmi6QL8Q== X-Received: by 2002:a9d:6487:: with SMTP id g7mr7250456otl.13.1633037173506; Thu, 30 Sep 2021 14:26:13 -0700 (PDT) Received: from mail-ot1-f47.google.com (mail-ot1-f47.google.com. [209.85.210.47]) by smtp.gmail.com with ESMTPSA id m26sm806392otf.12.2021.09.30.14.26.13 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 30 Sep 2021 14:26:13 -0700 (PDT) Received: by mail-ot1-f47.google.com with SMTP id g62-20020a9d2dc4000000b0054752cfbc59so9090801otb.1 for ; Thu, 30 Sep 2021 14:26:13 -0700 (PDT) X-Received: by 2002:a25:df06:: with SMTP id w6mr1562849ybg.459.1633036849801; Thu, 30 Sep 2021 14:20:49 -0700 (PDT) MIME-Version: 1.0 References: <20210930185031.18648-1-rppt@kernel.org> In-Reply-To: <20210930185031.18648-1-rppt@kernel.org> From: Linus Torvalds Date: Thu, 30 Sep 2021 14:20:33 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 0/6] memblock: cleanup memblock_free interface To: Mike Rapoport Cc: Linux Kernel Mailing List , Andrew Morton , Christophe Leroy , Juergen Gross , Mike Rapoport , Shahab Vahedi , devicetree , iommu , kasan-dev , KVM list , alpha , Linux ARM , linux-efi , "open list:BROADCOM NVRAM DRIVER" , Linux-MM , linux-riscv , linux-s390 , Linux-sh list , "open list:SYNOPSYS ARC ARCHITECTURE" , linux-um , linux-usb@vger.kernel.org, linuxppc-dev , linux-sparc , xen-devel@lists.xenproject.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-sh@vger.kernel.org On Thu, Sep 30, 2021 at 11:50 AM Mike Rapoport wrote: > > The first patch is a cleanup of numa_distance allocation in arch_numa I've > spotted during the conversion. > The second patch is a fix for Xen memory freeing on some of the error > paths. Well, at least patch 2 looks like something that should go into 5.15 and be marked for stable. Patch 1 looks like a trivial local cleanup, and could go in immediately. Patch 4 might be in that same category. The rest look like "next merge window" to me, since they are spread out and neither bugfixes nor tiny localized cleanups (iow renaming functions, global resulting search-and-replace things). So my gut feel is that two (maybe three) of these patches should go in asap, with three (maybe four) be left for 5.16. IOW, not trat this as a single series. Hmm? Linus