Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 16 Feb 2022 16:45:29 +0100
From:   Oscar Salvador <osalvador@suse.de>
To:     David Hildenbrand <david@redhat.com>
Cc:     linux-kernel@vger.kernel.org, linux-mm@kvack.org,
        Andrew Morton <akpm@linux-foundation.org>,
        "Rafael J. Wysocki" <rafael@kernel.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Michal Hocko <mhocko@suse.com>,
        Rafael Parra <rparrazo@redhat.com>
Subject: Re: [PATCH v2 2/2] drivers/base/memory: determine and store zone for
 single-zone memory blocks
Message-ID: <Yg0cGbrTA4bDEQHx@localhost.localdomain>
References: <20220210184359.235565-1-david@redhat.com>
 <20220210184359.235565-3-david@redhat.com>
 <YguFFRiNIktJhGnT@localhost.localdomain>
 <9738c049-a6a2-19f7-f9be-e7ae98c2c66b@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9738c049-a6a2-19f7-f9be-e7ae98c2c66b@redhat.com>
Precedence: bulk

On Wed, Feb 16, 2022 at 02:46:56PM +0100, David Hildenbrand wrote:
> And yes, add_memory_block() chould __init, that would also make it
> clearer out of which context init_memory_block() is called with
> MEM_ONLINE. I can send an addon patch for that!

Yeah, I think that would have helped me, and it definitely makes it more
clear, so go ahead ;-)


-- 
Oscar Salvador
SUSE Labs