Received: by 10.223.185.116 with SMTP id b49csp7688468wrg; Thu, 1 Mar 2018 09:24:09 -0800 (PST) X-Google-Smtp-Source: AG47ELsktdQw5o4fo6WYUxsTEpGGpjreAUiB9UR2qMQjoaFZL6AvnbzupMX8q9Y8w4DfGnrmczwU X-Received: by 10.99.126.24 with SMTP id z24mr2096721pgc.343.1519925049584; Thu, 01 Mar 2018 09:24:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519925049; cv=none; d=google.com; s=arc-20160816; b=l3QhmjLPPLRihh4f5ofMzPjTNXejYYy60uxC/Di2ICvyzPWlIBp2WjYIxtql0AqDIv 1GLCpeo0jhkrdYkSsJTVZYvx1yJOtxGv0owxSKnDZoiWbGTT4hUO3os5ctr8/tYscQHQ xKCMQu/fSEITi81o1Fpdv/yjeqY1dp+5AV1ohupt5Z/BOwWG81hFJuHqXBzn3GHCaHkt liiUGRXdn7jn9RlDERs2/MgsSZWLG765bUV/Z/0F6W/iEbEgQ/EilLhkcIKh653Y1U9P YkB2Bz5IOipflj8gIbkZ3Fx4DidK68YIVd9KsqVWHczzWbPaM7iJSDomUrTg0qUbxNwb 1S+g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature:dkim-signature :arc-authentication-results; bh=EX/N1lSO1pMiJt5wIwT1D05gUqIiIpJK69M90WAJRyE=; b=OnRU4NtwLbmMiPAGF2BsJPJZ63XV7Z1Ss03RGiT/oVMlIXSgsQSFxWfgUJaj8Y6N2C ut5JN+43CCSwiicMrPA3Fnfl1MSLAsoA+tmeBqiMmxbkLWwreGnFtYGIunDkhDM6c1JD jExiimJQiCpFFhc8KsLAiph9la7pQhW5rWcCpFwDNDx0tZmhHlyDz619vFJRQ1NEOz4j UHcM8OYzsjkuv2a1xa6/wasHyIjAXdVwJxGi902jH/DXbdAl6JAcKRIzM34JDG5aXtHz BmBa3PO/sPKphjTI7ZnJnQ82TD9D/CMQulgN9gEO7DSyiK+4+R3UimCxLX8XF4Fxx/vd 73Nw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=h5ezudmS; dkim=fail header.i=@linux-foundation.org header.s=google header.b=HCh+xLMf; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w12-v6si3253411plp.288.2018.03.01.09.23.54; Thu, 01 Mar 2018 09:24:09 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=h5ezudmS; dkim=fail header.i=@linux-foundation.org header.s=google header.b=HCh+xLMf; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1033413AbeCARXP (ORCPT + 99 others); Thu, 1 Mar 2018 12:23:15 -0500 Received: from mail-it0-f66.google.com ([209.85.214.66]:36722 "EHLO mail-it0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1033238AbeCARXM (ORCPT ); Thu, 1 Mar 2018 12:23:12 -0500 Received: by mail-it0-f66.google.com with SMTP id u5so8731878itc.1 for ; Thu, 01 Mar 2018 09:23:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=EX/N1lSO1pMiJt5wIwT1D05gUqIiIpJK69M90WAJRyE=; b=h5ezudmSxuI35gK3fwMhwE2wB7WQ31Ynuo0RmVE3U9mPoP3Qp3DZOu9/sC/T4Fe4qf QQZFxTLfOkJAqxcC+45QLz645GdRXhTw1EN+IJvx33bGvNNcDec6Xjc3rfr2B9oVSygt JFkmj3AwghBWZUfWl9XDFBbb2AyGmhqTl4EwBIA9nc+v8CjaXoKm2sGR6C5bwa+ZTPIH TAIyTXKcNcNDkCMZEaNadDf2F2A29pMOUWJ6uBTYM6Zu13cP4YeLiq3xrfH/AY04fk8u NCgiauzKuabEWEbYXJzJwgIYdJvMroSsnJz8395I5Nodw9u8OWQV2qt7RJDY/S17/Mda zzew== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=EX/N1lSO1pMiJt5wIwT1D05gUqIiIpJK69M90WAJRyE=; b=HCh+xLMfL2dj9P/b0F7vUnBJ+CsG1sZPfm8A3oIE69ef8Y94yRWveomXgfbWe/ElG7 vkh8WQI+LGkKJ7LF/5bkfCdA58Q5R+zXOkcY7QkjFkgjdkV2p+Q9Wf8vpEJ8p9Xxfrti xFGiBzBVmLwaihf8xGWgF1lCiyfJLqjU2rJ7U= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=EX/N1lSO1pMiJt5wIwT1D05gUqIiIpJK69M90WAJRyE=; b=BwIISQQrelSP2cr5gNw8/ZKOWCruVT92+NaoSVasoWBgjltFwm3/cMGwGZI+0UFs9f Qz7k0PntE8xqf67jVFJtgU4I7GFppZbgCibCgwKgXQA/kMpNu8G3cFscvE2eF/trAhgE v7uXHr456i8sNhQr+v3R0/jeFDhfv7LuoxIZ+BgQ8xDQkEG/tKci74gsULUdU9OpOQkv Yo5A1FiwPbzB05Ez47J8FAzeTV/mEMZTqG4clvVCJg8RmRUYS9UDkWduKDY/PAmoHl7j 0uZpzkJw03dqhE9NzSLa+oF7DkOz0Q985EMRKIev/Jtw8+ufG21hphmRUhHPRuy8BrzD z9Ng== X-Gm-Message-State: APf1xPA2yhhrvO7ELyc73koxpcVJnVgkzparqvSQVF/FxtwSNfIcDW8n dPsIE7GX8wGTIwQbu2pPJcuyty+jM69Mz0aFYRM= X-Received: by 10.36.135.195 with SMTP id f186mr3564740ite.100.1519924991291; Thu, 01 Mar 2018 09:23:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.135.221 with HTTP; Thu, 1 Mar 2018 09:23:10 -0800 (PST) In-Reply-To: <20180301163331.987775783@linutronix.de> References: <20180301163331.987775783@linutronix.de> From: Linus Torvalds Date: Thu, 1 Mar 2018 09:23:10 -0800 X-Google-Sender-Auth: _yOoBli6Ydv9sOMt8LgGsEoGcU4 Message-ID: Subject: Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME To: Thomas Gleixner Cc: LKML , Ingo Molnar , Peter Zijlstra , Steven Rostedt , John Stultz , Petr Mladek , Mark Salyzyn , Prarit Bhargava , Sergey Senozhatsky , Dmitry Torokhov , Kevin Easton , Michael Kerrisk , Jonathan Corbet Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote: > > This really needs lot of testing, documentation updates and more input from > userspace folks to make a final decision. Honestly, I don't think we'd get the testing this kind of change needs except by just trying it. I'm willing to merge this in the 4.17 merge window, with the understanding that if people end up reporting issues, we may just have to revert it all, and chalk it up to a learning experience - and add the appropriate commentary in the kernel code about exactly what it was that depended on that MONO/BOOT difference. One non-technical thing I would ask: use some other word than "conflate". Maybe just "combine". Or better yet, "unify". "Conflate" technically and historically means the same thing as combine, but has very much gathered a side meaning of "confuse". So yes, "conflate" is indeed about mixing or combining, but it's typically used in the sense of a *bad* combination or mixing. So "trying to conflate two issues" means "trying to mix two issues that are not the same into one". So "unify" and "conflate" mean both the same thing and almost exactly the opposite at the same time. And yes, you will find dictionaries (and linguists) that hold purely to the old meaning. As always, there are fogeys that can't get over the fact that meanings meander and change. Linus