[{"id":1754575,"web_url":"http://patchwork.ozlabs.org/comment/1754575/","msgid":"<20170823002911.y35nn7jkt34dvjbc@rob-hp-laptop>","list_archive_url":null,"date":"2017-08-23T00:29:11","subject":"Re: [RFC 1/3] dt-bindings: rtc: Add Realtek RTD1295","submitter":{"id":62529,"url":"http://patchwork.ozlabs.org/api/people/62529/","name":"Rob Herring (Arm)","email":"robh@kernel.org"},"content":"On Sun, Aug 20, 2017 at 03:36:29AM +0200, Andreas Färber wrote:\n> Add a binding for the RTC on the Realtek RTD119x/RTD129x SoC families.\n> \n> Signed-off-by: Andreas Färber \n> ---\n> .../devicetree/bindings/rtc/realtek,rtd119x.txt | 16 ++++++++++++++++\n> 1 file changed, 16 insertions(+)\n> create mode 100644 Documentation/devicetree/bindings/rtc/realtek,rtd119x.txt\n\nAcked-by: Rob Herring ","headers":{"Return-Path":"","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@bilbo.ozlabs.org","Authentication-Results":"ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=linux-rtc-owner@vger.kernel.org;\n\treceiver=)","Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xcSwW26x9z9s65\n\tfor ;\n\tWed, 23 Aug 2017 10:29:15 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1752789AbdHWA3O (ORCPT );\n\tTue, 22 Aug 2017 20:29:14 -0400","from mail-oi0-f67.google.com ([209.85.218.67]:37960 \"EHLO\n\tmail-oi0-f67.google.com\" rhost-flags-OK-OK-OK-OK) by vger.kernel.org\n\twith ESMTP id S1752628AbdHWA3N (ORCPT\n\t); Tue, 22 Aug 2017 20:29:13 -0400","by mail-oi0-f67.google.com with SMTP id j144so275603oib.5;\n\tTue, 22 Aug 2017 17:29:12 -0700 (PDT)","from localhost (216-188-254-6.dyn.grandenetworks.net.\n\t[216.188.254.6]) by smtp.gmail.com with ESMTPSA id\n\tn72sm321845oig.13.2017.08.22.17.29.11\n\t(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);\n\tTue, 22 Aug 2017 17:29:11 -0700 (PDT)"],"X-Google-DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=1e100.net; s=20161025;\n\th=x-gm-message-state:date:from:to:cc:subject:message-id:references\n\t:mime-version:content-disposition:content-transfer-encoding\n\t:in-reply-to:user-agent;\n\tbh=N/CpXi3Mj3foIypGw+e5I8icISrIPXLamLzj3Y157bI=;\n\tb=I2TK2QgfPgcIdzw5Qb2Bx2HVKiQeB1TdMCOS69gfgr++G6dEqZNnoIAk2/fIrygJNK\n\tLnbKhMmAz+qpbWEWJ2z8afZd5Q6Eu7CsJ9IYlsrfOlPYejAq+F3Gamwof5BvaMp41qIp\n\tQlZ4fY3U0VInaTFxo8vqGQ8dtlyDaVs1vBhdLe0JK2to5hBzK2fnpp6dtKeHC43swA4N\n\tYrTYwgG62faZZYXm8OIYlg8B1meGPTq1c/qML9U+syCWRW69NysHgJb7w7FK6m36jQ/w\n\tJGc61N6TbWXvkPcSwI0cfv+XHjSej4+D4h65U2Klc0gZfMh8vhrovVvFOvqHlmKHHlyx\n\ts/JA==","X-Gm-Message-State":"AHYfb5jVGR+LTuDc8B/scWUQJS2NQBjfb5KDtm5tmkEyFw1S35ovaXed\n\tWBoX/ruHjSJ7EA==","X-Received":"by 10.202.48.200 with SMTP id w191mr1084671oiw.161.1503448152529;\n\tTue, 22 Aug 2017 17:29:12 -0700 (PDT)","Date":"Tue, 22 Aug 2017 19:29:11 -0500","From":"Rob Herring ","To":"Andreas =?iso-8859-1?Q?F=E4rber?= ","Cc":"Alessandro Zummo ,\n\tAlexandre Belloni ,\n\tlinux-rtc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,\n\tlinux-kernel@vger.kernel.org, Roc He ,\n\t=?utf-8?B?6JKL5Li955C0?= ,\n\tMark Rutland , devicetree@vger.kernel.org","Subject":"Re: [RFC 1/3] dt-bindings: rtc: Add Realtek RTD1295","Message-ID":"<20170823002911.y35nn7jkt34dvjbc@rob-hp-laptop>","References":"<20170820013632.18375-1-afaerber@suse.de>\n\t<20170820013632.18375-2-afaerber@suse.de>","MIME-Version":"1.0","Content-Type":"text/plain; charset=iso-8859-1","Content-Disposition":"inline","Content-Transfer-Encoding":"8bit","In-Reply-To":"<20170820013632.18375-2-afaerber@suse.de>","User-Agent":"NeoMutt/20170113 (1.7.2)","Sender":"linux-rtc-owner@vger.kernel.org","Precedence":"bulk","List-ID":"","X-Mailing-List":"linux-rtc@vger.kernel.org"}},{"id":1758242,"web_url":"http://patchwork.ozlabs.org/comment/1758242/","msgid":"<629b9ed0-7b2d-7c5c-20b8-17289a76f097@suse.de>","list_archive_url":null,"date":"2017-08-27T10:41:46","subject":"Re: [RFC 1/3] dt-bindings: rtc: Add Realtek RTD1295","submitter":{"id":9542,"url":"http://patchwork.ozlabs.org/api/people/9542/","name":"Andreas Färber","email":"afaerber@suse.de"},"content":"Hi Rob,\n\nAm 23.08.2017 um 02:29 schrieb Rob Herring:\n> On Sun, Aug 20, 2017 at 03:36:29AM +0200, Andreas Färber wrote:\n>> Add a binding for the RTC on the Realtek RTD119x/RTD129x SoC families.\n>>\n>> Signed-off-by: Andreas Färber \n>> ---\n>> .../devicetree/bindings/rtc/realtek,rtd119x.txt | 16 ++++++++++++++++\n>> 1 file changed, 16 insertions(+)\n>> create mode 100644 Documentation/devicetree/bindings/rtc/realtek,rtd119x.txt\n> \n> Acked-by: Rob Herring \n\nThanks. Did you read the RFC question in the cover letter as well and\nhave any comments? Downstream has an rtc-base-year = <2014>; property\nthat I had left out in this RFC and due to your ack not included in v2.\n\nShould we default to 2014 in the driver and add an optional base-year\nproperty once we encounter a diverging device, or should we make it\nrequired from the beginning? I did not spot any other rtc binding with\nsuch a property and would appreciate a clarification.\n\nThanks in advance,\n\nAndreas","headers":{"Return-Path":"","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@bilbo.ozlabs.org","Authentication-Results":"ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=linux-rtc-owner@vger.kernel.org;\n\treceiver=)","Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xgBKq3j1lz9sP5\n\tfor ;\n\tSun, 27 Aug 2017 20:42:07 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1751271AbdH0Klu (ORCPT );\n\tSun, 27 Aug 2017 06:41:50 -0400","from mx2.suse.de ([195.135.220.15]:36426 \"EHLO mx1.suse.de\"\n\trhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP\n\tid S1751189AbdH0Klt (ORCPT );\n\tSun, 27 Aug 2017 06:41:49 -0400","from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254])\n\tby mx1.suse.de (Postfix) with ESMTP id 18400AABA;\n\tSun, 27 Aug 2017 10:41:48 +0000 (UTC)"],"X-Virus-Scanned":"by amavisd-new at test-mx.suse.de","Subject":"Re: [RFC 1/3] dt-bindings: rtc: Add Realtek RTD1295","To":"Rob Herring ","Cc":"Alessandro Zummo , Alexandre Belloni\n\t, linux-rtc@vger.kernel.org,\n\tlinux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,\n\tRoc He , =?utf-8?b?6JKL5Li955C0?=\n\t, Mark Rutland ,\n\tdevicetree@vger.kernel.org","References":"<20170820013632.18375-1-afaerber@suse.de>\n\t<20170820013632.18375-2-afaerber@suse.de>\n\t<20170823002911.y35nn7jkt34dvjbc@rob-hp-laptop>","From":"=?utf-8?q?Andreas_F=C3=A4rber?= ","Organization":"SUSE Linux GmbH","Message-ID":"<629b9ed0-7b2d-7c5c-20b8-17289a76f097@suse.de>","Date":"Sun, 27 Aug 2017 12:41:46 +0200","User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101\n\tThunderbird/52.2.1","MIME-Version":"1.0","In-Reply-To":"<20170823002911.y35nn7jkt34dvjbc@rob-hp-laptop>","Content-Type":"text/plain; charset=utf-8","Content-Language":"en-US","Content-Transfer-Encoding":"8bit","Sender":"linux-rtc-owner@vger.kernel.org","Precedence":"bulk","List-ID":"","X-Mailing-List":"linux-rtc@vger.kernel.org"}},{"id":1758262,"web_url":"http://patchwork.ozlabs.org/comment/1758262/","msgid":"<20170827134729.GE13622@lunn.ch>","list_archive_url":null,"date":"2017-08-27T13:47:29","subject":"Re: [RFC 1/3] dt-bindings: rtc: Add Realtek RTD1295","submitter":{"id":13608,"url":"http://patchwork.ozlabs.org/api/people/13608/","name":"Andrew Lunn","email":"andrew@lunn.ch"},"content":"> Thanks. Did you read the RFC question in the cover letter as well and\n> have any comments? Downstream has an rtc-base-year = <2014>; property\n> that I had left out in this RFC and due to your ack not included in v2.\n> \n> Should we default to 2014 in the driver and add an optional base-year\n> property once we encounter a diverging device, or should we make it\n> required from the beginning? I did not spot any other rtc binding with\n> such a property and would appreciate a clarification.\n\nHi Andreas\n\nFrom the perspective of the hardware, does it care what the base is?\n\nA device using a different base will initially return the wrong\ntime. But once the correct time has been written back, it will be O.K.\n\nThis only becomes an issue if a device is used with different OSs,\nwhich have different bases. Swapping back and forth between OSs then\nbecomes an issue.\n\nKISS suggests not having a base in DT until it is actually\nrequired. Since it is an additional property, it does not break\nbackwards compatibility when added.\n\n\t Andrew","headers":{"Return-Path":"","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@bilbo.ozlabs.org","Authentication-Results":"ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=linux-rtc-owner@vger.kernel.org;\n\treceiver=)","Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xgGRz3l3Gz9s8V\n\tfor ;\n\tSun, 27 Aug 2017 23:47:43 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1751392AbdH0Nrm (ORCPT );\n\tSun, 27 Aug 2017 09:47:42 -0400","from vps0.lunn.ch ([178.209.37.122]:45422 \"EHLO vps0.lunn.ch\"\n\trhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP\n\tid S1751338AbdH0Nrm (ORCPT );\n\tSun, 27 Aug 2017 09:47:42 -0400","from andrew by vps0.lunn.ch with local (Exim 4.84_2)\n\t(envelope-from )\n\tid 1dlxuT-0000bq-1Z; Sun, 27 Aug 2017 15:47:29 +0200"],"Date":"Sun, 27 Aug 2017 15:47:29 +0200","From":"Andrew Lunn ","To":"Andreas =?iso-8859-1?q?F=E4rber?= ","Cc":"Rob Herring , linux-rtc@vger.kernel.org,\n\tAlessandro Zummo ,\n\tRoc He , devicetree@vger.kernel.org,\n\t????????? , linux-kernel@vger.kernel.org,\n\tAlexandre Belloni ,\n\tMark Rutland , linux-arm-kernel@lists.infradead.org","Subject":"Re: [RFC 1/3] dt-bindings: rtc: Add Realtek RTD1295","Message-ID":"<20170827134729.GE13622@lunn.ch>","References":"<20170820013632.18375-1-afaerber@suse.de>\n\t<20170820013632.18375-2-afaerber@suse.de>\n\t<20170823002911.y35nn7jkt34dvjbc@rob-hp-laptop>\n\t<629b9ed0-7b2d-7c5c-20b8-17289a76f097@suse.de>","MIME-Version":"1.0","Content-Type":"text/plain; charset=us-ascii","Content-Disposition":"inline","In-Reply-To":"<629b9ed0-7b2d-7c5c-20b8-17289a76f097@suse.de>","User-Agent":"Mutt/1.5.23 (2014-03-12)","Sender":"linux-rtc-owner@vger.kernel.org","Precedence":"bulk","List-ID":"","X-Mailing-List":"linux-rtc@vger.kernel.org"}},{"id":1758286,"web_url":"http://patchwork.ozlabs.org/comment/1758286/","msgid":"","list_archive_url":null,"date":"2017-08-27T17:26:11","subject":"Re: [RFC 1/3] dt-bindings: rtc: Add Realtek RTD1295","submitter":{"id":9542,"url":"http://patchwork.ozlabs.org/api/people/9542/","name":"Andreas Färber","email":"afaerber@suse.de"},"content":"Hi Andrew,\n\nAm 27.08.2017 um 15:47 schrieb Andrew Lunn:\n>> Thanks. Did you read the RFC question in the cover letter as well and\n>> have any comments? Downstream has an rtc-base-year = <2014>; property\n>> that I had left out in this RFC and due to your ack not included in v2.\n>>\n>> Should we default to 2014 in the driver and add an optional base-year\n>> property once we encounter a diverging device, or should we make it\n>> required from the beginning? I did not spot any other rtc binding with\n>> such a property and would appreciate a clarification.\n> \n> From the perspective of the hardware, does it care what the base is?\n\nThe hardware stores a 15-bit number of days since Jan 1st of that base\nyear. It does not store the base year.\n\nThe datasheet does not name such a base year. No manual is available.\n\nThe driver needs to get it from somewhere for calculating day/month/year\nin read_time and days in set_time.\n\nThe read_offset/set_offset API appeared to be something different.\n\n> A device using a different base will initially return the wrong\n> time. But once the correct time has been written back, it will be O.K.\n> \n> This only becomes an issue if a device is used with different OSs,\n> which have different bases. Swapping back and forth between OSs then\n> becomes an issue.\n\nThese are TV boxes, so yes, I'm dual-booting into Android with a vendor\n4.1 kernel and would like to keep date compatibility.\n\nhttps://en.opensuse.org/HCL:Zidoo_X9S\nhttps://en.opensuse.org/HCL:ProBox2_Ava\nhttps://en.opensuse.org/HCL:Lake1\n\nAs stated in the v2 rtc commit message, 2014 is the base year\nencountered on all three devices that I've had access to.\n@Jiang, if you're using a different base year, please speak up!\n\n> KISS suggests not having a base in DT until it is actually\n> required. Since it is an additional property, it does not break\n> backwards compatibility when added.\n\nThat's what I've attempted here - but for RDA8810PL serial Rob said he\ndid not want future changes to my binding, therefore I am asking for his\nconfirmation here.\n\nRegards,\nAndreas","headers":{"Return-Path":"","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@bilbo.ozlabs.org","Authentication-Results":"ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=linux-rtc-owner@vger.kernel.org;\n\treceiver=)","Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xgMJN477Jz9s7m\n\tfor ;\n\tMon, 28 Aug 2017 03:26:28 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1751260AbdH0R0P (ORCPT );\n\tSun, 27 Aug 2017 13:26:15 -0400","from mx2.suse.de ([195.135.220.15]:50356 \"EHLO mx1.suse.de\"\n\trhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP\n\tid S1751182AbdH0R0O (ORCPT );\n\tSun, 27 Aug 2017 13:26:14 -0400","from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254])\n\tby mx1.suse.de (Postfix) with ESMTP id D8F21ABA6;\n\tSun, 27 Aug 2017 17:26:12 +0000 (UTC)"],"X-Virus-Scanned":"by amavisd-new at test-mx.suse.de","Subject":"Re: [RFC 1/3] dt-bindings: rtc: Add Realtek RTD1295","To":"Andrew Lunn ","Cc":"Rob Herring , linux-rtc@vger.kernel.org,\n\tAlessandro Zummo ,\n\tRoc He , devicetree@vger.kernel.org,\n\t????????? , linux-kernel@vger.kernel.org,\n\tAlexandre Belloni ,\n\tMark Rutland , linux-arm-kernel@lists.infradead.org","References":"<20170820013632.18375-1-afaerber@suse.de>\n\t<20170820013632.18375-2-afaerber@suse.de>\n\t<20170823002911.y35nn7jkt34dvjbc@rob-hp-laptop>\n\t<629b9ed0-7b2d-7c5c-20b8-17289a76f097@suse.de>\n\t<20170827134729.GE13622@lunn.ch>","From":"=?utf-8?q?Andreas_F=C3=A4rber?= ","Organization":"SUSE Linux GmbH","Message-ID":"","Date":"Sun, 27 Aug 2017 19:26:11 +0200","User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101\n\tThunderbird/52.2.1","MIME-Version":"1.0","In-Reply-To":"<20170827134729.GE13622@lunn.ch>","Content-Type":"text/plain; charset=utf-8","Content-Language":"en-US","Content-Transfer-Encoding":"8bit","Sender":"linux-rtc-owner@vger.kernel.org","Precedence":"bulk","List-ID":"","X-Mailing-List":"linux-rtc@vger.kernel.org"}},{"id":1758293,"web_url":"http://patchwork.ozlabs.org/comment/1758293/","msgid":"<20170827190749.6njixw7cxwbhmclp@piout.net>","list_archive_url":null,"date":"2017-08-27T19:07:49","subject":"Re: [RFC 1/3] dt-bindings: rtc: Add Realtek RTD1295","submitter":{"id":26276,"url":"http://patchwork.ozlabs.org/api/people/26276/","name":"Alexandre Belloni","email":"alexandre.belloni@free-electrons.com"},"content":"On 27/08/2017 at 19:26:11 +0200, Andreas Färber wrote:\n> Hi Andrew,\n> \n> Am 27.08.2017 um 15:47 schrieb Andrew Lunn:\n> >> Thanks. Did you read the RFC question in the cover letter as well and\n> >> have any comments? Downstream has an rtc-base-year = <2014>; property\n> >> that I had left out in this RFC and due to your ack not included in v2.\n> >>\n> >> Should we default to 2014 in the driver and add an optional base-year\n> >> property once we encounter a diverging device, or should we make it\n> >> required from the beginning? I did not spot any other rtc binding with\n> >> such a property and would appreciate a clarification.\n> > \n> > From the perspective of the hardware, does it care what the base is?\n> \n> The hardware stores a 15-bit number of days since Jan 1st of that base\n> year. It does not store the base year.\n> \n> The datasheet does not name such a base year. No manual is available.\n> \n> The driver needs to get it from somewhere for calculating day/month/year\n> in read_time and days in set_time.\n> \n> The read_offset/set_offset API appeared to be something different.\n> \n\nThere is no api to change the epoch of an RTC because it is difficult to\ndo in a race free way. This has to be worked on.\n\nAnyway, you don't really care for now as it goes up to 2093 and\nhopefully, you will never have a product with a different epoch.\n\n> > A device using a different base will initially return the wrong\n> > time. But once the correct time has been written back, it will be O.K.\n> > \n\nThe other issue being that you don't have any way to know whether the\nbase is correct or not until the date is set.\n\n> > This only becomes an issue if a device is used with different OSs,\n> > which have different bases. Swapping back and forth between OSs then\n> > becomes an issue.\n> \n> These are TV boxes, so yes, I'm dual-booting into Android with a vendor\n> 4.1 kernel and would like to keep date compatibility.\n> \n> https://en.opensuse.org/HCL:Zidoo_X9S\n> https://en.opensuse.org/HCL:ProBox2_Ava\n> https://en.opensuse.org/HCL:Lake1\n> \n> As stated in the v2 rtc commit message, 2014 is the base year\n> encountered on all three devices that I've had access to.\n> @Jiang, if you're using a different base year, please speak up!\n> \n> > KISS suggests not having a base in DT until it is actually\n> > required. Since it is an additional property, it does not break\n> > backwards compatibility when added.\n> \n> That's what I've attempted here - but for RDA8810PL serial Rob said he\n> did not want future changes to my binding, therefore I am asking for his\n> confirmation here.\n\nIt would be a change that is easy enough to do in a backward compatible\nway so that is probably fine.","headers":{"Return-Path":"","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@bilbo.ozlabs.org","Authentication-Results":"ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=linux-rtc-owner@vger.kernel.org;\n\treceiver=)","Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xgPYQ2NTkz9s7f\n\tfor ;\n\tMon, 28 Aug 2017 05:07:54 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1751291AbdH0THx (ORCPT );\n\tSun, 27 Aug 2017 15:07:53 -0400","from mail.free-electrons.com ([62.4.15.54]:58996 \"EHLO\n\tmail.free-electrons.com\" rhost-flags-OK-OK-OK-OK) by vger.kernel.org\n\twith ESMTP id S1751264AbdH0THw (ORCPT\n\t); Sun, 27 Aug 2017 15:07:52 -0400","by mail.free-electrons.com (Postfix, from userid 110)\n\tid 770D920A2A; Sun, 27 Aug 2017 21:07:49 +0200 (CEST)","from localhost (unknown [88.191.26.124])\n\tby mail.free-electrons.com (Postfix) with ESMTPSA id 3AABF20A08;\n\tSun, 27 Aug 2017 21:07:49 +0200 (CEST)"],"X-Spam-Checker-Version":"SpamAssassin 3.4.0 (2014-02-07) on\n\tmail.free-electrons.com","X-Spam-Level":"","X-Spam-Status":"No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT\n\tshortcircuit=ham autolearn=disabled version=3.4.0","Date":"Sun, 27 Aug 2017 21:07:49 +0200","From":"Alexandre Belloni ","To":"Andreas =?iso-8859-1?q?F=E4rber?= ","Cc":"Andrew Lunn , Rob Herring ,\n\tlinux-rtc@vger.kernel.org, Alessandro Zummo ,\n\tRoc He , devicetree@vger.kernel.org,\n\t????????? ,\n\tlinux-kernel@vger.kernel.org, Mark Rutland ,\n\tlinux-arm-kernel@lists.infradead.org","Subject":"Re: [RFC 1/3] dt-bindings: rtc: Add Realtek RTD1295","Message-ID":"<20170827190749.6njixw7cxwbhmclp@piout.net>","References":"<20170820013632.18375-1-afaerber@suse.de>\n\t<20170820013632.18375-2-afaerber@suse.de>\n\t<20170823002911.y35nn7jkt34dvjbc@rob-hp-laptop>\n\t<629b9ed0-7b2d-7c5c-20b8-17289a76f097@suse.de>\n\t<20170827134729.GE13622@lunn.ch>\n\t","MIME-Version":"1.0","Content-Type":"text/plain; charset=iso-8859-1","Content-Disposition":"inline","Content-Transfer-Encoding":"8bit","In-Reply-To":"","User-Agent":"NeoMutt/20170609 (1.8.3)","Sender":"linux-rtc-owner@vger.kernel.org","Precedence":"bulk","List-ID":"","X-Mailing-List":"linux-rtc@vger.kernel.org"}}]