From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
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>
Subject: [rtc-linux] Re: [PATCH 1/1] rtc: fix type information of rtc-proc
Date: Thu, 12 Nov 2015 10:05:48 +0800 [thread overview]
Message-ID: <5643F3FC.8000102@huawei.com> (raw)
In-Reply-To: <20151111105450.GC4519@piout.net>
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
>>
>>
>
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
WARNING: multiple messages have this Message-ID (diff)
From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
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>
Subject: Re: [PATCH 1/1] rtc: fix type information of rtc-proc
Date: Thu, 12 Nov 2015 10:05:48 +0800 [thread overview]
Message-ID: <5643F3FC.8000102@huawei.com> (raw)
In-Reply-To: <20151111105450.GC4519@piout.net>
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
>>
>>
>
next prev parent reply other threads:[~2015-11-12 2:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 9:47 [rtc-linux] [PATCH 1/1] rtc: fix type information of rtc-proc Zhen Lei
2015-10-08 9:47 ` Zhen Lei
2015-10-17 11:22 ` [rtc-linux] " Alexandre Belloni
2015-10-17 11:22 ` Alexandre Belloni
2015-11-11 1:06 ` [rtc-linux] " Leizhen (ThunderTown)
2015-11-11 1:06 ` Leizhen (ThunderTown)
2015-11-11 10:54 ` [rtc-linux] " Alexandre Belloni
2015-11-11 10:54 ` Alexandre Belloni
2015-11-12 2:05 ` Leizhen (ThunderTown) [this message]
2015-11-12 2:05 ` Leizhen (ThunderTown)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5643F3FC.8000102@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=arnd@arndb.de \
--cc=dingtianhong@huawei.com \
--cc=guohanjun@huawei.com \
--cc=huxinwei@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=rtc-linux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.