From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-178.mta1.migadu.com (out-178.mta1.migadu.com [95.215.58.178]) (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 9F1AA413629; Tue, 9 Jun 2026 12:08:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.178 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781006923; cv=none; b=PIOtiXx80zfhQ14515IvT+ahD7szfxKoW32aQDUg0pYNfd/VO2C2MydDafwVScJs/C994Q7aKojbncpBk0zYKx855230FafpsfKmewbXb58blJYGpFZn0FxR161d5n5+IGEm0+0zFmuzVMFd+I1xA+kNULz693ocl6zYy+LQAtQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781006923; c=relaxed/simple; bh=Nqf3YO87WrzNM7BINtAtbxa7Cdud+kVMGo0EvPdnscA=; h=Date:From:To:CC:Subject:In-Reply-To:References:Message-ID: MIME-Version:Content-Type; b=MFA4LwPqEkx4aze+omj2pn+XrMCKfDsu1b11Ad2dUj+8+Grf4HrkAA0TKwU6GKyllWqlEFvHi9nNgwMneNNv7Ct/A8leyDpouEAL0dUeyuHfalDLeGsQBqqydQpPoo8uGiHVFF0+2DUrufYW8043PQyDkoZbmIJJUZhE6SB1ADQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=Y8ydkJ8Q; arc=none smtp.client-ip=95.215.58.178 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="Y8ydkJ8Q" Date: Tue, 09 Jun 2026 13:08:34 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1781006918; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Nqf3YO87WrzNM7BINtAtbxa7Cdud+kVMGo0EvPdnscA=; b=Y8ydkJ8Q7hKiAkSBYm2L1fsTLlc7q6yC4yt9ROlmA5zV0wfixbVwGG4h3kcrF0VJE9qyem cRZll3fqnQ1E6+MfCjXT/2NZo3P1ouC24Ja6X12spkE2gN/b9ldBiImbCB4/vt2H4ohG7b CB6vy+umI997iqhYjb3f6Cyf5+YwVZ0= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Igor Korotin To: Wolfram Sang , rust-for-linux@vger.kernel.org CC: Wolfram Sang , linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, Danilo Krummrich Subject: Re: [GIT PULL] rust-i2c-fixes for 7.1-rc7 In-Reply-To: References: <9e49b71b-8b60-479e-93e7-5c12e352c78e@linux.dev> Message-ID: <5633BA97-5666-45C8-A024-87A737A4086A@linux.dev> Precedence: bulk X-Mailing-List: rust-for-linux@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 X-Migadu-Flow: FLOW_OUT Hello Wolfram On June 9, 2026 10:26:40 AM GMT+01:00, Wolfram Sang wrote: >Hi all, > >(adding a few more people to CC to have a potentially bigger discussion) > >> Please be already aware that from 7=2E2 on, you will need send pull >> requests to Andi who takes over the I2C subsystem=2E I will write a >> seperate mail about the handover later today=2E > >Done now [1]=2E On a second thought, after pulling in the I2C abstraction= s >a few times now, I wonder meanwhile if the Rust-tree wouldn't be the >better path to upstream=2E The abstractions are way more Rust than they >are I2C=2E And potential merge-conflicts come from generic Rust >abstraction updates, not from I2C=2E > >This is Andi's choice now, of course=2E Just wanted to give my 2 cents >here=2E=2E=2E Thanks for the heads-up on the handover =E2=80=94 noted, I'll direct pull = requests to Andi from 7=2E2 onward=2E On the Rust-tree question: I don't have a strong preference either way fro= m a workflow perspective, but technically your reasoning makes sense to me= =2E As long as the changes don't introduce or alter any I2C-specific behavi= or =E2=80=94 and so far they don't =E2=80=94 routing them through the Rust = tree seems like the more natural fit, and would avoid spurious merge confli= cts driven by generic abstraction updates rather than anything I2C-related= =2E Ultimately Andi's call, of course=2E Happy to adapt to whatever process wo= rks best=2E Cheers Igor