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 5A1981F16B; Wed, 26 Feb 2025 16:31:32 +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=1740587492; cv=none; b=j8oqQw7OU/wP1mTQw/HKJPDW60+UDWq3L++jTNA/re+X1zD5NpM047mr1MPYity5s4A1olnkU1PPv+gAOP3qaeAp5RyCUrhQ/tCdJncSf4ivQ/QlvKDyFZTkZpmIW+PhjZdMcbu6FxFr/UNjlojiD4lb4EU7GOmwHDdhCsEVIzc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740587492; c=relaxed/simple; bh=fbUyMbVzemgHgNjXulx1F/b+A8SvYzgDEV9k1ywZNr0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=qEGNPgBTtR+b0IRXJQLbvQshzE1IzZ6ykheNulRTKZlgPr3kBV4GfhXCPHaaiZO//DtzvN4p6svTTLiVHS/NO5uGhXtpcHk7vnfnn/Meb2TkhzznsIsvVq85swNgYVjlcnozoubSog8bGa9dTlvV98T1QDTtwMa3WngZ+Eo/AWw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=JNTEV8UQ; 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="JNTEV8UQ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 689E0C4CED6; Wed, 26 Feb 2025 16:31:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1740587491; bh=fbUyMbVzemgHgNjXulx1F/b+A8SvYzgDEV9k1ywZNr0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=JNTEV8UQ3w24YfxS2uL9nYsCo2h26uXzC+2iBxJ4wI6zk8ghUfiZDM4PkSyqpGjIu VwzzGVCfYRJuUwN2smbBoyQ0r1vjwvY8ht8mPeKMQgmVH2tlQJSH7+t8GX8vkdJYT3 1msT3nxeKjxSgvA62ZyCbNaHmpbNRSkFFsfKLXYX+ZgCMwylrx4BS7TJIbZFWpNGf/ zR5GcADgmdevAYk7qWcvPXASC5cdgi35rGmqetWoUXEs8HWirRQ8Hv/25XYUB4/AkQ fzvX1gL09nMp5SZKd1CWhZvEzsEhoo/6BQSgLsOC8ndfc8pZ/HFjb0zA+LdlbiUUPc dlEgOIMtp2h6g== Date: Wed, 26 Feb 2025 17:31:29 +0100 From: Frederic Weisbecker To: Andreas Hindborg Cc: Boqun Feng , Miguel Ojeda , Anna-Maria Behnsen , Thomas Gleixner , Danilo Krummrich , Alex Gaynor , Gary Guo , =?iso-8859-1?Q?Bj=F6rn?= Roy Baron , Benno Lossin , Alice Ryhl , Trevor Gross , Lyude Paul , Guangbo Cui <2407018371@qq.com>, Dirk Behme , Daniel Almeida , Tamir Duberstein , rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org, Miguel Ojeda Subject: Re: [PATCH v9 01/13] rust: hrtimer: introduce hrtimer support Message-ID: References: <87msebyxtv.fsf@kernel.org> <4UoaifxB7JgBVKsNQyFR_T8yc3Vtn5TLAEdxdXrojNmOzJSEncopauEyjDpnbqzr8Z74ZWjd_N-bB-BwBS-7aQ==@protonmail.internalid> <87bjuryvb0.fsf@kernel.org> 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=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <87bjuryvb0.fsf@kernel.org> Le Mon, Feb 24, 2025 at 08:52:35PM +0100, Andreas Hindborg a écrit : > > It's of course up to hrtimer maintainers. But I personally nack this > > kconfig, because it's not necessary, and hrtimer API has been stable for > > a while. > > Having the switch is fine for me, removing it is fine as well. It's just > an added convenience that might come in handy. But having this kconfig > very close to zero overhead, so I do not really understand your > objection. I would like to better understand your reasoning. If you choose to make a such a Kconfig switch, it would only make sense in order to spare some bytes when no drivers use it for example. But if you're afraid that the Rust binding is on the way while the core is changing some API then I guess simply disabling Rust would be enough for testing. I don't think it's necessary (unless it's strictly selected by drivers). But it's your call. Thanks. > > > Best regards, > Andreas Hindborg > >