From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.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 B095344D031; Tue, 10 Mar 2026 10:25:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773138356; cv=none; b=ass6LkK6TVPo9MHp9Z9GRLLKk8VvsL6tws+ONhvle5OX5avJZebAI0fWCu2XK5G4S3eTJkYtakAGavJULTB6bMPDSXEHulvi8KqvSaeXwzgk93JKxsISxu+lC9Zxnt5/sswGrKaNGymaAK6Miz1XCToNqeu8BvJDkCxeHYaldBU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773138356; c=relaxed/simple; bh=bhAW5MOmZUjx9mkQj11fGuIHG+Yc4g2ly/sx9of0FAI=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=P67ZVz4HElFq+ooWCkGREM5bhvv5xAaYcmwJrbFrcUstdfNCaSg/XtaT1xhFuBVGyOdstN2Uq9bDbbtNcyPcoj/4FOEBWegQ3nbvbMgqfVD5N7ftA+Qk5WBD3eCZWKzz8s6vdq3Fb3V2ncuHHhq+8RDpbphvqdJnoqDGnHrqI6Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=ORNGBZbc; arc=none smtp.client-ip=198.175.65.18 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="ORNGBZbc" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1773138355; x=1804674355; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=bhAW5MOmZUjx9mkQj11fGuIHG+Yc4g2ly/sx9of0FAI=; b=ORNGBZbchF7fnpgyn9hRJkKw8cOUw+kFOuYc4JJi1PcgFYoLEu7AaThF 9zh417KQH4y1vn0EKHOxQ/bRzoi2nzUxXazq0c8Y+iqfIt2gBMI+V3s2R sN5ViuBzBkWzHSIWiXXOHZ8DAfpX+DCSPJTnYy/ybbc4rP8PYQK7h9x3n rp3V3ySjSiCsuWp0SkrU2/wk6CsLlkh58ivkq1QJ5qheCR2Z04YD8BqmC IDv0XRnQn6iHlb57KV1G+I+/bryu4GYpNzeLwi3fqxrs0IT/TvkAnF+98 q1iBPuzZ5ENW0/2fo1ZqKTsOEXBnXTVPxwtE6rDi/gHZj8gaCmw9encCt w==; X-CSE-ConnectionGUID: p/W6o4qVQ7qssjSshMOBRw== X-CSE-MsgGUID: w+crc9ECTGqpoPDNfS70iQ== X-IronPort-AV: E=McAfee;i="6800,10657,11724"; a="74221908" X-IronPort-AV: E=Sophos;i="6.23,112,1770624000"; d="scan'208";a="74221908" Received: from fmviesa005.fm.intel.com ([10.60.135.145]) by orvoesa110.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Mar 2026 03:25:55 -0700 X-CSE-ConnectionGUID: TxIVIO7FTw+AaShQreaqXg== X-CSE-MsgGUID: Dsp9Ut7RTHC1moU7/K+jSw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.23,112,1770624000"; d="scan'208";a="224755127" Received: from vpanait-mobl.ger.corp.intel.com (HELO localhost) ([10.245.244.54]) by fmviesa005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Mar 2026 03:25:52 -0700 Date: Tue, 10 Mar 2026 12:25:50 +0200 From: Andy Shevchenko To: Lee Jones Cc: Brian Mak , Herve Codina , linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH v2] mfd: core: Preserve OF node when ACPI handle is present Message-ID: References: <20260226224511.458065-1-makb@juniper.net> <20260306133806.GM183676@google.com> <20260310092148.GE183676@google.com> Precedence: bulk X-Mailing-List: stable@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: <20260310092148.GE183676@google.com> Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo On Tue, Mar 10, 2026 at 09:21:48AM +0000, Lee Jones wrote: > On Fri, 06 Mar 2026, Andy Shevchenko wrote: > > On Fri, Mar 06, 2026 at 01:38:06PM +0000, Lee Jones wrote: > > > On Thu, 26 Feb 2026, Brian Mak wrote: ... > > > > + /* > > > > + * FIXME: The fwnode design doesn't allow proper stacking/sharing. This > > > > > > So when will this be fixed exactly? > > > > I don't know, it's a huge task that requires of redesigning how struct > > fwnode_handle looks like and how it cohabits with struct device. Do you > > you think that NOTE will be more appropriate, because it may span several > > releases. > > If someone is going to do the work sometime in the near future, it can > stay as FIXME. A few releases isn't going to offend anyone. However, > if we're just going to sit on it and this is likely to be here for an > elongated period, it should be changed. Then better to be just a NOTE:. > Any idea who is planning on working on it? I am not sure anyone is planning on working on this in the near future. We see the problem, but it hasn't hit someone's work too much to become a showstopper (some workarounds, or not fully correct, but acceptable behaviour was a way out so far). -- With Best Regards, Andy Shevchenko