From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4CF94363C5E for ; Tue, 28 Jul 2026 16:07:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785254859; cv=none; b=nuY60x7iFslZqgbm9gCie7+tEhD9DGGZ2lnacV9YD8fFsYM1YtiGcW40tot9j+EGRPLI60cvQkrPKZI66ZjQc9CXpAqHyDE/hYkLTgW+E0lCUqwdAgttx9pY0WWa7GgR3OlvM3yMEL/JTRLo7SkQg3LIO9er3GJTjfesnz56uJ0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785254859; c=relaxed/simple; bh=IJh1kGiqnhtmfU/jmZmc4sHx3akgeMIv255E69o3Mkc=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=qILHxY+Kqp+9QgjcXMNTchVzgcjjjcfdqZhsuEgNK5NqOn2mNef+F5QfSUWTqHf1Gem8mrP/rTNUEE1IitoDFckPuBddJMX8IdJZ8ryy8qDs6CsVkiJnJVux44Y79lvb+XkOm9UUxI3fy2HpRCiJSLp4g4BYsUl7D+m2T7iCJRQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=do9Qf31f; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="do9Qf31f" Received: by smtp.kernel.org (Postfix) with ESMTPSA id BAA8D1F000E9; Tue, 28 Jul 2026 16:07:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1785254857; bh=1d8NjVYJJn+wjjiK3UWZkRgmZ9sB7Xz8XibGwlAR4TU=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=do9Qf31f+8z39RaavaLnmBkTzfJzmuRlrk8+c6DfkV589EUCL9anWdb2KW+CMNtWO nrtuVp3Rl2+Ob8SWcEcEgDQDmBmreziaWFdrI6Yya8u6sJo92w2Sj2eF6lkknMnbx5 GswKhL3Abrgsq6uXH23uuN3kfiyB2ZAqwbRqDM15Tnm2MV06pRD43C/kEUuTbiNpZ5 eFujT+vDCoUOvMALJ+z87C7KGHWB/GVtPB7tOshxTpI2jwQtcUuhT1mpVkEPKrdSYm Ssw8TFKkcDDJ/UEBU1loEG+wuv0jrBPxS0Kxb0zv5waA+ONOdsvZbCu6gb2ZomxRa3 OW3+Vdr61M8/w== Date: Tue, 28 Jul 2026 19:07:30 +0300 From: Mike Rapoport To: Pratyush Yadav Cc: Pasha Tatashin , Alexander Graf , Muchun Song , Oscar Salvador , David Hildenbrand , Andrew Morton , Jason Miu , Jork Loeser , kexec@lists.infradead.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 00/21] kho: make boot time huge page allocation work nicely with KHO Message-ID: References: <20260725172133.4018491-1-pratyush@kernel.org> <2vxzecgn89jt.fsf@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2vxzecgn89jt.fsf@kernel.org> On Tue, Jul 28, 2026 at 04:37:26PM +0200, Pratyush Yadav wrote: > On Tue, Jul 28 2026, Mike Rapoport wrote: > > > > Please take a look at Sashiko comments, we might need v5 if it has valid > > (not pre-existing) points. > > I took a quick look and the only valid points I can see are the ones on > patch 19/21 "memblock: make HugeTLB bootmem allocation work with KHO". > > All others are pre-existing problems. > > Is it okay if I send a single follow up patch to fix 19/21? Or would you > prefer a full respin? I prefer a full respin please :) > Also, general thing, but I should go and fix all the pre-existing > problems too at some point. I sent a fix for a really simple one > already, but Sashiko has found other problems too... Yeah, that's true for any subsystem nowadays. > -- > Regards, > Pratyush Yadav -- Sincerely yours, Mike.