From: Ozgur <ozgur@goosey.org>
To: Aishwarya Pant <aishpant@gmail.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Julia Lawall <julia.lawall@lip6.fr>, Jonathan Corbet <corbet@lwn.net>
Subject: Re: rtc: sysfs: move sysfs interface to Documentation/ABI
Date: Thu, 28 Dec 2017 17:23:33 +0300 [thread overview]
Message-ID: <480511514471013@web35j.yandex.ru> (raw)
In-Reply-To: <434381514470951@web50o.yandex.ru>
28.12.2017, 17:22, "Ozgur" <okaratas@yandex.com>:
> 28.12.2017, 16:31, "Aishwarya Pant" <aishpant@gmail.com>:
>> Hi
Hello,
>> In Documentation/rtc.txt, there is a description of the sysfs
>> interface which could be moved to Documentation/ABI.
>>
>> Would such a change be useful?
>>
>> The ABI documentation format looks like the following:
>>
>> What: (the full sysfs path of the attribute)
>> Date: (date of creation)
>> KernelVersion: (kernel version it first showed up in)
>> Contact: (primary contact)
>> Description: (long description on usage)
>>
>> I am doing this in an exercise to move sysfs ABI interfaces (which are
>> documented) to their right place i.e. in Documentation/ABI along with the rest.
Do I understand right? Are you want to make the rtc.txt part the same format as ABI folder?
for example create to RTC folder and add /dev/rtc what, date, kernelversion, contact right?
This can be a good idea and I can help.
>> Aishwarya
Ozgur
next prev parent reply other threads:[~2017-12-28 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 13:31 rtc: sysfs: move sysfs interface to Documentation/ABI Aishwarya Pant
2017-12-28 14:22 ` Ozgur
2017-12-28 14:23 ` Ozgur [this message]
2017-12-28 15:00 ` Aishwarya Pant
2017-12-28 18:30 ` Ozgur
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=480511514471013@web35j.yandex.ru \
--to=ozgur@goosey.org \
--cc=a.zummo@towertech.it \
--cc=aishpant@gmail.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=corbet@lwn.net \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox