From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752432AbbKKKyy (ORCPT ); Wed, 11 Nov 2015 05:54:54 -0500 Received: from down.free-electrons.com ([37.187.137.238]:55598 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751059AbbKKKyv (ORCPT ); Wed, 11 Nov 2015 05:54:51 -0500 Date: Wed, 11 Nov 2015 11:54:50 +0100 From: Alexandre Belloni To: "Leizhen (ThunderTown)" Cc: Alessandro Zummo , rtc-linux , linux-kernel , Arnd Bergmann , Zefan Li , Xinwei Hu , Tianhong Ding , Hanjun Guo Subject: Re: [PATCH 1/1] rtc: fix type information of rtc-proc Message-ID: <20151111105450.GC4519@piout.net> References: <1444297652-10328-1-git-send-email-thunder.leizhen@huawei.com> <564294AB.1080500@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <564294AB.1080500@huawei.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. > > 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 > > -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com