From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 D4465431A57 for ; Mon, 3 Aug 2026 18:07:22 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785780444; cv=none; b=f2AXsw9muTieTlyTgVIiMxXPb1HcpVwrN0jT2/lfP6MzpG7sorZZRzQ733POtnt1vPhs4ZJ4RIhkVr2HM3BVx8ZbM6/ZtvMBvmmNHdSloQFvTgaQSKh9b4clhKOGQdmjcvcl6MHgXD+YmniA5HlTMjCVoR8AfK1AzngpLqlebeY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785780444; c=relaxed/simple; bh=Pgh0s3vUI1Fy/x6XRCRneGgcdsEZoBTx1UsQr7kJgvI=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Xdvoaj6QcB7fe5eIaksmj7v7lKNXVuj2GMXdUTHNyTgklAHzQ4S7IoPMOuhV89c5eH+FWuRW7DDYvondDze7Ys2OEKrPfSfzsEUerII/cy4YL1KoAjcYMWyH23xfR4Vlq3+texxwp5RD8GsV4695xlybdkma4lXOJNROpKYHVOU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=HhLl/M/1; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="HhLl/M/1" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E0BB21F000E9; Mon, 3 Aug 2026 18:07:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1785780442; bh=RVBgpTAPx0QaWF/iESlvF9lQKXld+lgSa5L4KQZMoqQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=HhLl/M/1qKiYFjOcU4GCcarv8EbNmI8hc6N95BUMpYPtFrQsc5Xc2aeGhVK/V3KVo J3AjzdP89AumfqhOzwFGLEMjBVE8pPZwI920/xThkmFEKW6tZ9FFuMkq1K9dWR05dx yPqNpUL0cVvsBFqLvJUAov6s7OUkYNtwOd9CXRbRPY63FZZo0Ktrj9EeZztApnj0f7 PFbH/vOCAXcts9j5XIjm6gvZmSYKUsZkgTN8lWGPykFNnqKoMOj5VlrO9FWmjYL0D4 hHj7M16cTiVPhIR9hXSvkR60cGb/EI/Rn7NEpv3QPkVaPozut5wjt4O+/K+14DdLZt uDAOZ7/zAZizQ== Date: Mon, 3 Aug 2026 08:07:19 -1000 From: Keith Busch To: Daniel Colascione Cc: Jens Axboe , Christoph Hellwig , Sagi Grimberg , linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] nvme: make sending wall-clock time to NVMe opt-in Message-ID: References: <20260713203443.322748-1-dancol@dancol.org> <87qzl6k3bx.fsf@dancol.org> <87ldaoh08v.fsf@dancol.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ldaoh08v.fsf@dancol.org> On Sun, Aug 02, 2026 at 01:59:28PM -0400, Daniel Colascione wrote: > Daniel Colascione writes: > > I mostly care about having *some* knob to turn this off. Right now, it's > > unconditional. I'm happy with either opt-in or opt-out, although I have > > a weak preference for the former. > > Ping. Is there anything I should be addressing in the patch? Thanks The historic behavior is that the timestamp feature happens. Making an option to change behavior usually leaves the historic behavior the default so that anything using it isn't suddenly having to scramble to restore what they had before.