From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (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 98F2D39E16F for ; Wed, 14 Jan 2026 15:22:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768404153; cv=none; b=butdWq+EMnk4mjSWkoWWO3R3C6I1TK0SCGY2wxdxziXtfvhLtN8ETr/cRSwAgfY67L3IZNkA5UOUQSQWyvctNWPPvEbBChn+IquL7rZDDkkzFe6W9zM7CXKAYgfuh4Mk7A7b1A7v0S4jIaGlv9x+KqHjtBiTj0TUG318abaWBzQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768404153; c=relaxed/simple; bh=m4v/R7D3jy8vrI2Fks1W5QkC0M+VIHll9pL494k4YqE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=kuNg4o8Fp8SrlEDOdIRgvU/1pD0oem7yCJG7oqM94FiwLTLhUazONyYzGOevpKROR9TIE/lz7IolvFUU24Gc6+9h5EbbymBFWIO7ygp5R8E8s3oXlYDbGclhksfms5zak8BfAlKajspA8SsSoDPjKlUjy8g+EGRl4Y7ckMY0N6A= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=bBclkT4U; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="bBclkT4U" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=k1; bh=E4Fb p1gWprjaWwTIF67PnzL6ErW/s4uVu2YzVoPvCqc=; b=bBclkT4UKNVbybJbFbtT 2IDSjfq04crf0WEXCzSgltWp6wpqj0IOcdpzcamA3rcrrPUCv+MNqmhDSkzgCpG2 yyUwkpFnxeiwWAsDNIjvzpXCnAKA7CfPCL6C/npvQA4uZy1ffvHBROEEWiILU9LQ T5fieVkn9r7JIKV3w9VndZef1veocFlhmQAS4lhzcPxSvtPjH272MMONUlJRjdJp 0oBKq5rFA2R7i8VND/Ovz3Osry5WRtbS33bnNHtrOtvIqUGOXGrACp1MRRFz7UDn VR5kCfSzjz3kuQKrzSlOZBOoYuNaAEV9BRlqH5T7WrM24MhSiotV6b5jeW1eXHro 5w== Received: (qmail 2192941 invoked from network); 14 Jan 2026 16:22:18 +0100 Received: by mail.zeus03.de with UTF8SMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 14 Jan 2026 16:22:18 +0100 X-UD-Smtp-Session: l3s3148p1@2rR5rFpIEqgujnsM Date: Wed, 14 Jan 2026 16:22:17 +0100 From: Wolfram Sang To: Bartosz Golaszewski Cc: Bartosz Golaszewski , Andi Shyti , Chen-Yu Tsai , Jernej Skrabec , Samuel Holland , Khalil Blaiech , Asmaa Mnebhi , Jean Delvare , Madhavan Srinivasan , Michael Ellerman , Nicholas Piggin , "Christophe Leroy (CS GROUP)" , Andreas =?utf-8?Q?F=C3=A4rber?= , Manivannan Sadhasivam , linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-sunxi@lists.linux.dev, linuxppc-dev@lists.ozlabs.org, linux-actions@lists.infradead.org Subject: Re: [PATCH 00/12] i2c: add and start using i2c_adapter-specific printk helpers Message-ID: References: <20251223-i2c-printk-helpers-v1-0-46a08306afdb@oss.qualcomm.com> Precedence: bulk X-Mailing-List: linux-sunxi@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: > FYI: I think the road-map will look something like this: v7.1 will get > new interfaces and most controllers under drivers/i2c/ converted as > this can be done within your tree exclusively. For v7.2 (with the new > interfaces upstream) we can think about converting all i2c controller > drivers treewide to the new helpers. Once v7.2-rc1 is tagged, I would > try to remove struct device from struct i2c_adapter locally and send > it to autobuilders for testing. If that goes well, we could create > struct i2c_adapter_private or something like this and store its > address in struct i2c_adapter. This new struct would be controlled by > i2c core and contain struct device. With that out of the way, for v7.4 > we could think about adding SRCU into the mix (possibly using the > then-available revocable). > > If all goes well, we should be done in early 2027. :) With this plan, what could possibly go wrong? :)