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 86E8527A465; Tue, 24 Feb 2026 15:36:21 +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=1771947381; cv=none; b=kWHawtgysNYyGjrVE1UZU6NUb0y41gdGQv9apN5IxDOv9hDg/ftKbufCyXEtayeB2kL36N8El//0E8NPSp7cgzcWRk839s+ioUec7/lvFG/1x+n7CZIfjRofKoqjnTMXafiIs336UaexUs8ZhW9T8/vY2Zp2DbdPGAGUpv6adqE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771947381; c=relaxed/simple; bh=3Fq4GyJ51xygSCu4g96ES50MGDoQvCKhfJ11zDmethE=; h=Mime-Version:Content-Type:Date:Message-Id:Subject:Cc:To:From: References:In-Reply-To; b=nTw35E7JA15NVe7INBiW/HQGgQrpmg6G1n0qmSX3J65U/OnL1ZPifZQORT7DTDQvl7VVO2Bc9rFT7850mTek9LlqY872kmsQ4sgT1Mz4xkhPbvS1yzNqia/dED0MRrcjIX9y/i0ID2lJkquyMGn9QK/AqzbQa/uYsAfuch//tpc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=V05JHQdj; 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="V05JHQdj" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5F903C19422; Tue, 24 Feb 2026 15:36:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1771947381; bh=3Fq4GyJ51xygSCu4g96ES50MGDoQvCKhfJ11zDmethE=; h=Date:Subject:Cc:To:From:References:In-Reply-To:From; b=V05JHQdjXUaavBY/eaiRrALYDMQ2tLZvX6VLUigiA7Ke4oXt4wODd47X/qD+9Y6MB j2Mw/yLzfJ4qOoGZxdP18wFJsWpB7G1OVqmjpS8y/6TAbxTwf+QN51JkhaX1ltl9Yt nJvcyuRuDdewt3VIuysU4tNJUjysbmjFquBrKqLHCFDAV14YvSHGkLoyO1yIaLvCDp wdNIcwuzAEauv6ELh3fRPA+wP3QHqtvkiszHwsPZUBfNWIKxDPjBB0WAaPU+7rKw+a E4B5rry6QZ/nwVPXtW/iotdmisBqgkL6Kl1r/zNJZFizIfzh8bdxl4S8XZssqCuVqI fkvSH4h9IqMCw== Precedence: bulk X-Mailing-List: rust-for-linux@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Tue, 24 Feb 2026 16:36:16 +0100 Message-Id: Subject: Re: [RFC PATCH v3 1/5] rtc: add device selector for rtc_class_ops callbacks Cc: "Alexandre Belloni" , "Alvin Sun" , "Miguel Ojeda" , "Boqun Feng" , "Gary Guo" , =?utf-8?q?Bj=C3=B6rn_Roy_Baron?= , "Benno Lossin" , "Andreas Hindborg" , "Alice Ryhl" , "Trevor Gross" , , , "Greg Kroah-Hartman" To: "Rafael J. Wysocki" From: "Danilo Krummrich" References: <20260221111619162a41a1@mail.local> <20260222000556ea1938c0@mail.local> <20260224145721a9e69e4d@mail.local> In-Reply-To: On Tue Feb 24, 2026 at 4:23 PM CET, Rafael J. Wysocki wrote: > On the C side it really depends on what probe (of the parent) does. > If it sets driver_data of the parent before registering the RTC > device, then it'll all work. If it registers the RTC device before > setting driver_data for the parent, there may be a race. > > IIUC, the idea on the Rust side is to use the capabilities of the > compiler to eliminate the possibility of messing up the ordering in a > driver. Yes, this is all spot-on.