From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-40134.protonmail.ch (mail-40134.protonmail.ch [185.70.40.134]) (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 3D0E339ACC; Fri, 7 Mar 2025 13:23:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.70.40.134 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741353803; cv=none; b=XG/g7aMiJANcPBSSDcG9Y9YNGYH2FdTbBFOYJaZZcEIPXZJLVLNE4dBUUumM8Jl6BaqmEokp1eECYZoX2cJscRRmCZ8d+r+2/HRXtDLVuGTaCavScTw3l319i5RILfSWDHQfuoBwcLCiXIzx6Sp33PUGXJ718yyRiDrNSTE2oUU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741353803; c=relaxed/simple; bh=4WxMkD6CWyChQWUEG9Os74cWrdBRR9i/mnauP29FhQA=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=vFMcIbufijHHrtnvVsqUvWCXbdWc1Q1GaSY3V2020O6kDusLDSGTsCrvRHLZSDCB/lzzgmOn2DH4He5AnRrOyfPICitA8QevysvznIeB6ZBOmGETyLD13Jq1KTDezS0puaJHR65ak70b/jzVp1SBfGVaTzCRC2xqCUfiKhEBxjM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=proton.me; spf=pass smtp.mailfrom=proton.me; dkim=pass (2048-bit key) header.d=proton.me header.i=@proton.me header.b=OVtHNwYT; arc=none smtp.client-ip=185.70.40.134 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=proton.me Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=proton.me Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=proton.me header.i=@proton.me header.b="OVtHNwYT" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=protonmail; t=1741353800; x=1741613000; bh=4WxMkD6CWyChQWUEG9Os74cWrdBRR9i/mnauP29FhQA=; 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:List-Unsubscribe:List-Unsubscribe-Post; b=OVtHNwYTOnfPsM5SvBMF8K8nqWh2pTMDquHO8MEK+SNTE2q4odDI5WQ/Q6G7shTp1 GZGJy4/xHWlZto/RLuWVxkRzQgMePqqwOy6sSgNmslLN24gIkkn/tb6eeTVgPt8hcX AaAMRVVqp/7nSpL+pv2g0RAE808bO3JyQvk8yX+/Oj7+/j9Sx8qDa6E+VsXq0nbRxQ kAs2JSAMCgkSmbmz7ll/LmcnzMtG1GjsTbc/x/nPPAl1L16YSzNSCLcfq52zwXubfl kCKHb8xiRJU6Jo0ljgsKhK+UI6O91fWgF1a8xE1d3HK7vK7bWi25xA6i7Hyz+B7z3+ HOzxvD2TWce/w== Date: Fri, 07 Mar 2025 13:23:15 +0000 To: Andreas Hindborg , Miguel Ojeda , Anna-Maria Behnsen , Frederic Weisbecker , Thomas Gleixner , Danilo Krummrich From: Benno Lossin Cc: Alex Gaynor , Boqun Feng , Gary Guo , =?utf-8?Q?Bj=C3=B6rn_Roy_Baron?= , Alice Ryhl , Trevor Gross , Lyude Paul , Guangbo Cui <2407018371@qq.com>, Dirk Behme , Daniel Almeida , Tamir Duberstein , Markus Elfring , rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v10 12/13] rust: hrtimer: add clocksource selection through `ClockId` Message-ID: In-Reply-To: <20250307-hrtimer-v3-v6-12-rc2-v10-12-0cf7e9491da4@kernel.org> References: <20250307-hrtimer-v3-v6-12-rc2-v10-0-0cf7e9491da4@kernel.org> <20250307-hrtimer-v3-v6-12-rc2-v10-12-0cf7e9491da4@kernel.org> Feedback-ID: 71780778:user:proton X-Pm-Message-ID: 2b7d2f67b764e6bff4b81e640caa986fcc2b35ef 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 On Fri Mar 7, 2025 at 11:11 AM CET, Andreas Hindborg wrote: > Allow selecting a clock source for timers by passing a `ClockId` > variant to `HrTimer::new`. > > Acked-by: Frederic Weisbecker > Reviewed-by: Lyude Paul > Signed-off-by: Andreas Hindborg Reviewed-by: Benno Lossin --- Cheers, Benno