Received: by 2002:a05:7208:9594:b0:7e:5202:c8b4 with SMTP id gs20csp914167rbb; Sun, 25 Feb 2024 09:36:20 -0800 (PST) X-Forwarded-Encrypted: i=2; AJvYcCUbb5xhHT2MSNij1HhDsOA6RAFpvdkPeYFsinJbssvoF3ju9a1cJYKnYZJsTtswYey2aA+ADlE4lGPOjCuwtVO+xmWKbI5l7ZTKj7GwWQ== X-Google-Smtp-Source: AGHT+IFqygPg42VR5RxoMZnlKOWP0MjcI+Oetb5Jy3z9fOWphKyum3QwnkCbE3QTNWz2ACYne2uC X-Received: by 2002:a17:903:2342:b0:1db:b5c3:d2b2 with SMTP id c2-20020a170903234200b001dbb5c3d2b2mr6277177plh.57.1708882579908; Sun, 25 Feb 2024 09:36:19 -0800 (PST) Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [2604:1380:45e3:2400::1]) by mx.google.com with ESMTPS id w22-20020a1709026f1600b001d9642def85si2341560plk.202.2024.02.25.09.36.19 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 25 Feb 2024 09:36:19 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-80235-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@pm.me header.s=protonmail3 header.b=ckuTE90Q; arc=fail (body hash mismatch); spf=pass (google.com: domain of linux-kernel+bounces-80235-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-80235-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=QUARANTINE) header.from=pm.me Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 9BC692818C9 for ; Sun, 25 Feb 2024 17:36:19 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id BBAF81AAA5; Sun, 25 Feb 2024 17:36:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=pm.me header.i=@pm.me header.b="ckuTE90Q" Received: from mail-4316.protonmail.ch (mail-4316.protonmail.ch [185.70.43.16]) (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 7065F18B1B for ; Sun, 25 Feb 2024 17:36:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.70.43.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708882573; cv=none; b=md6urpwa67HmyHcVizIaD1lQX1w8stAi933nk1TYUHp5RU6ZE/JaQJ6rfUYCsgBwLYQP12XrLXHHMmWRPrGkeMy0OADa3Abc7BoLqF5gXmIBceYyt1samEveonDBYM608jvsx/x9TrAjvQxabcJIsNK1SDpmtznWkXuUJhc2s9o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708882573; c=relaxed/simple; bh=4lhzB69Iuo/Z5wWUbCxtDG7+U02BeKBwQXu94Rz2GIE=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=lVBrXcMRjyioeCaxq0My+/G+zwTl78s7+ueYQqiz0BL/zO2Y0MCMMQu6y2z9b4oX/CBoHxyQiyIlhObiA94E2hvhaWpJ63KUKcuf0Y79fK+tFUs5eQPTdhIxa6OZrFyo7wwO+n/gMvmOe9Zw8sw4P3XQWeGAJ3LC3gAB6WL7lI0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=pm.me; spf=pass smtp.mailfrom=pm.me; dkim=pass (2048-bit key) header.d=pm.me header.i=@pm.me header.b=ckuTE90Q; arc=none smtp.client-ip=185.70.43.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=pm.me Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=pm.me DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pm.me; s=protonmail3; t=1708882562; x=1709141762; bh=4lhzB69Iuo/Z5wWUbCxtDG7+U02BeKBwQXu94Rz2GIE=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=ckuTE90Qbek7pBioZbbkC4yupNCWVCg+l681yf8ZG7EaCekoSF6o9t0bGmDmodiqo PWBvUXUxZ+TuidO+5syld+5p/217N9QNqnWpHqlZP1QhLOZW7AJXOWvnx571J0wpsv 8tBSrXxJyasYNuah1513j+TEzms/bpFv3T8WfW3H1YcW7rLbz60NjabO9ld9mmUK7K pNGqNU3WMP2RvwkeOv65G2wEG5BDYabUl2vOnM5hPMdlk2nBEqrI8A05CZqTIIbBUO 8J5zdVbb1d5c+Armpd/QknubgxBXzUee9M+VijGZbmksJYpvM1J0z6hFqJJib2Jh3w 0yg9um4rItQtQ== Date: Sun, 25 Feb 2024 17:35:43 +0000 To: Miquel Raynal From: Michael Pratt Cc: devicetree@vger.kernel.org, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, saravanak@google.com, abel.vesa@linaro.org, alexander.stein@ew.tq-group.com, andriy.shevchenko@linux.intel.com, bigunclemax@gmail.com, brgl@bgdev.pl, colin.foster@in-advantage.com, djrscally@gmail.com, dmitry.baryshkov@linaro.org, festevam@gmail.com, fido_max@inbox.ru, frowand.list@gmail.com, geert@linux-m68k.org, heikki.krogerus@linux.intel.com, kernel@pengutronix.de, linus.walleij@linaro.org, linux@roeck-us.net, luca.weiss@fairphone.com, magnus.damm@gmail.com, martin.kepplinger@puri.sm, rafal@milecki.pl, ansuelsmth@gmail.com, richard@nod.at, sakari.ailus@linux.intel.com, sudeep.holla@arm.com, tglx@linutronix.de, tony@atomide.com, vigneshr@ti.com, dianders@chromium.org, jpb@kernel.org, rafael@kernel.org Subject: Re: [PATCH v1 4/4] mtd: mtdpart: Allow fwnode links to NVMEM compatible fwnodes Message-ID: In-Reply-To: <20240205161129.1889a943@xps-13> References: <20240123014517.5787-1-mcpratt@pm.me> <20240123014517.5787-5-mcpratt@pm.me> <20240205161129.1889a943@xps-13> Feedback-ID: 27397442:user:proton 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=utf-8 Content-Transfer-Encoding: quoted-printable Hi Miquel, Sorry for the wait in replying. On Monday, February 5th, 2024 at 10:11, Miquel Raynal wrote: =20 >=20 > Hi Michael, >=20 > mcpratt@pm.me wrote on Tue, 23 Jan 2024 01:47:21 +0000: >=20 > > This reverts commit fb42378dcc7f247df56f0ecddfdae85487495fbc > > ("mtd: mtdpart: Don't create platform device that'll never probe"). > >=20 > > That commit is a manual named exception in order to avoid fw_devlink li= nks > > to an "nvmem-cells" compatible node which is a descendant of the fwnode > > that represents the real supplier device that probes. > >=20 > > The commit does not work for newer cases, like the "fixed-layout" >=20 >=20 > Do you have plans for it? Because it is the modern description that is > now expected, so I don't feel convinced by all this work (which is > nevertheless considerable) if fixed-layouts are still broken? >=20 Sorry for the misunderstanding, I was referring to the already existing com= mit cited in the message when saying "The commit does not work for newer cases.= ." which is why reverting it in this patch is part of the series. I'll reword = it. >=20 >=20 > Thanks, > Miqu=C3=A8l