Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp991756ybn; Wed, 2 Oct 2019 09:14:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqxTiu8P9KDOwZp8xVVGhCNTLLnIdd7oGLs3r6u0IWnlco1DZi4G/XytoVewMaAU3UZRpapl X-Received: by 2002:a17:906:c7d4:: with SMTP id dc20mr3751493ejb.235.1570032841051; Wed, 02 Oct 2019 09:14:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570032841; cv=none; d=google.com; s=arc-20160816; b=uS5XFOO4gAGUFVMKB9WvA+1Kd3rFsjG5gKlkqBGcMrKi9+CN85qc1cFqyvyG3WfNW9 PAG0WyAKWR/gsPYTLdre1dDMENZQrw6O4ZbBxMHBzxS0e29fAlJkdN8m9TdCRrOPT6go D3RkGaIjTxd0iOo0sWGjjlpmRpkSHIie04RPDFW5PrfMTfSZq/E/EyBDnlm3A9at2HBN YbtVljvSmZ3i83nDV+yK69Zx3Tauh7Oi88tXql1wfwpWCpOLLqjxm5HvUNbk6PJrDWCS SRnkX+s7+kJxFp1nc2+6qD4QHGI+/doXbGOtJGVSoiemMmzU0OAg6L7yjrByTE2T24bT 51IQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=4lxUAYVST+yoISpCagq97QW+HMjX2RFJxIfmv7iL+lc=; b=lFWbN+kbWO7PHN4WtiFO+Ldb6T5lyQdrAup5KM1PzH9FLDgNoN4vP9yX+k1mloda2C Cl3zKjBJxB4f63nyRk7nM/kkR5C8sUir/nILtAYYfOvtHJ4VSrVAoOXvmrIreqs6ygBQ OO5qZuqr/lF0H06L8Cnok6LJythoL5jlcdP9aZgZrvHZ2LIrby2K1Zxepmt84Tvbsz9x kfLo+q2bBMr9kCZzV6/PwDUPde3qDEgZMNPKHs8owWE44tIddN4f+VJ37YxhonAvWEzP 5XHqiEVY1j5VP7gab6SD0dcQiDFLUeYYd25wG6wDWmqTujmE+vRTZzNMkw48IZReOENY x3bA== ARC-Authentication-Results: i=1; mx.google.com; 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 c14si13508717eda.8.2019.10.02.09.13.36; Wed, 02 Oct 2019 09:14:01 -0700 (PDT) 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; 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 S1728876AbfJBPeN (ORCPT + 99 others); Wed, 2 Oct 2019 11:34:13 -0400 Received: from relay7-d.mail.gandi.net ([217.70.183.200]:40423 "EHLO relay7-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728793AbfJBPeN (ORCPT ); Wed, 2 Oct 2019 11:34:13 -0400 X-Originating-IP: 86.207.98.53 Received: from localhost (aclermont-ferrand-651-1-259-53.w86-207.abo.wanadoo.fr [86.207.98.53]) (Authenticated sender: alexandre.belloni@bootlin.com) by relay7-d.mail.gandi.net (Postfix) with ESMTPSA id 1635E20006; Wed, 2 Oct 2019 15:34:10 +0000 (UTC) Date: Wed, 2 Oct 2019 17:34:10 +0200 From: Alexandre Belloni To: Dmitry Torokhov Cc: Nick Crews , Alessandro Zummo , linux-rtc@vger.kernel.org, lkml , Pavel Machek , enric.balletbo@collabora.com, Benson Leung , dlaurie@chromium.org, Daniel Kurtz Subject: Re: [PATCH v3] rtc: wilco-ec: Handle reading invalid times Message-ID: <20191002153410.GO4106@piout.net> References: <20190925203209.79941-1-ncrews@chromium.org> <20191001195342.GH4106@piout.net> <20191002103236.GM4106@piout.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/10/2019 08:20:34-0700, Dmitry Torokhov wrote: > > I'm still not convinced it is useful to have an error in dmesg when the > > time is invalid, as long as userspace knows it is invalid. What is the > > course of action for the end user when that happens? > > Report it, or, in our case, we will see it in the feedback logs. > However I do agree that it is not the best option, even if we report > error to userspace I am not sure if it will handle it properly. What > userspace is supposed to do when presented with -EIO or similar? > I would say probably retry a few times if it gets -EIO and simply abort in case of -EINVAL. I'm not aware of any userspace tool behaving that way though. They all simply abort. -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com