From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 C51B7242D62 for ; Sun, 3 May 2026 01:42:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777772559; cv=none; b=B6TdWv3+IAxzcLe/BdX9v6Ql80HolbrQJ+UZSw22k2ipcBsG7DysbHoLWJaHwki60bO556Csco/NdVCBgnBBZw7UxQm7mpEWqoIKh4ignY3wYWpEmynU0cKMnaMpMfbHPjWc7KdJ0P2wc/eZDMcmkbHiBCwJ/oSCmFZqp9QjEfo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777772559; c=relaxed/simple; bh=xuhveDWH858rTx5QLCxAx3Y1Nm0rC6y3u+ot2Q41dO4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=N43Bw5lEQEBeOcww3EnB+paPDnZqCJ5yJ1Su19KRMD/QCmo08ApwraVTE+Gy4iQPQlof6cyEhqjrmWVsQ/dy273d8p4gopdblELmrQaAeztNvDKckxkS2JjykEehz5X5GDCnLuor7CO4px2ABFDMRbo43jtFVp8uSoLjUKK1aBM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=jnKxhHm9; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="jnKxhHm9" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4CE0BC19425; Sun, 3 May 2026 01:42:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1777772559; bh=xuhveDWH858rTx5QLCxAx3Y1Nm0rC6y3u+ot2Q41dO4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jnKxhHm9NDW15t2Yb/QG2Tj/8hZkK4+VYQ/u9My3W0fHJ1DBztn9m0qc3xbZ6NSnV uLlYCPmdUHQCo8FQnqmgr+tNz35KR+naS/J0b3UlBu7n3pZP9nSM3Xm27HWqL/BW04 BYpMwi6F6fRxei56xkRR3xrW/7bvh1paxN/ykIQ4+h+EUPNIwK2c3g6dvWfW6wD5lp OzhqZ7VfsvL4QtvW06hg8FeGk26wdfP3Gc3DdqkOLNRin6dYrnCSwFVzE6qNlfYMMi tIUm5yxDiYhyNfnOv2KFSG4sfasRDUoEdLejWbvXyLAAtCwbUHhlnY7bHDKxXOmq64 HjK/QYc/4Df8w== Date: Sun, 3 May 2026 09:42:35 +0800 From: Tzung-Bi Shih To: Titouan Ameline de Cadeville Cc: jwerner@chromium.org, briannorris@chromium.org, chrome-platform@lists.linuxfoundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3] coreboot_table: skip failing entries instead of aborting populate Message-ID: References: <20260501094322.123160-1-titouan.ameline@gmail.com> 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: <20260501094322.123160-1-titouan.ameline@gmail.com> On Fri, May 01, 2026 at 11:43:22AM +0200, Titouan Ameline de Cadeville wrote: > coreboot_table_populate() registers devices one by one. If > device_register() fails for one entry, the current code returns > immediately, leaving previously registered devices orphaned on the > coreboot bus with no cleanup path. > > Since coreboot table entries are independent of each other, a failure > on one entry should not prevent the others from being registered. > This mirrors the strategy used by of_platform_populate(), which skips > individual failures rather than aborting. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-firmware-next [1/1] coreboot_table: skip failing entries instead of aborting populate commit: 86e3bbc716332600e9e087f8a4889f4d9714a99c Thanks!