From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752812AbbKLCJl (ORCPT <rfc822;w@1wt.eu>);
	Wed, 11 Nov 2015 21:09:41 -0500
Received: from szxga01-in.huawei.com ([58.251.152.64]:30769 "EHLO
	szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752340AbbKLCJj (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 11 Nov 2015 21:09:39 -0500
Subject: Re: [PATCH 1/1] rtc: fix type information of rtc-proc
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
References: <1444297652-10328-1-git-send-email-thunder.leizhen@huawei.com>
 <564294AB.1080500@huawei.com> <20151111105450.GC4519@piout.net>
CC: Alessandro Zummo <a.zummo@towertech.it>,
        rtc-linux <rtc-linux@googlegroups.com>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        Arnd Bergmann <arnd@arndb.de>, Zefan Li <lizefan@huawei.com>,
        Xinwei Hu <huxinwei@huawei.com>,
        Tianhong Ding <dingtianhong@huawei.com>,
        Hanjun Guo <guohanjun@huawei.com>
From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
Message-ID: <5643F3FC.8000102@huawei.com>
Date: Thu, 12 Nov 2015 10:05:48 +0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <20151111105450.GC4519@piout.net>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.177.23.164]
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0),
	refid=str=0001.0A020206.5643F406.013F,ss=1,re=0.000,fgs=0,
	ip=0.0.0.0,
	so=2013-06-18 04:22:30,
	dmn=2011-05-27 18:58:46
X-Mirapoint-Loop-Id: adab9042ba635bced83246c7c46d6f33
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org



On 2015/11/11 18:54, Alexandre Belloni wrote:
> On 11/11/2015 at 09:06:51 +0800, Leizhen (ThunderTown) wrote :
>> Hi, all
>>
>> I'm sorry. Maybe I didn't describe clearly enough before. These words are finally
>> shown to the end user. The end user maybe not a programmer, abbreviation word is unsuitable.
>>
> 
> Yes, that is exactly m point. What if an end user currently has a
> program parsing the file and looking for alrm_time or alrm_date? After
> updating his kernel, the program won't work anymore which is something
> we don't want.

OK. I see. Thanks.

> 
>>
>> cat /proc/driver/rtc
>>
>> rtc_time        : 00:47:43
>> rtc_date        : 2015-11-11
>> alrm_time       : 03:27:58				//alrm_time --> alarm_time
>> alrm_date       : 2015-10-08				//alrm_date --> alarm_date
>> alarm_IRQ       : no
>> alrm_pending    : no					//alrm_pending --> alarm_pending
>> update IRQ enabled      : no
>>
>>
>