From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: rtc-linux@googlegroups.com
Cc: linux-kernel@vger.kernel.org, a.zummo@towertech.it
Subject: Re: [rtc-linux] Re: [PATCH 1/2] rtc: Document the sysfs interface
Date: Fri, 4 Sep 2009 17:52:06 +0100 [thread overview]
Message-ID: <20090904165206.GF1576@sirena.org.uk> (raw)
In-Reply-To: <20090904163918.GA25419@srcf.ucam.org>
On Fri, Sep 04, 2009 at 05:39:18PM +0100, Matthew Garrett wrote:
> On Fri, Sep 04, 2009 at 05:35:21PM +0100, Mark Brown wrote:
> > Wouldn't this be better placed under Documentation/ABI?
> Unsure. I'd assumed it made more sense in the existing docs.
My understanding is that the sysfs ABI (and ABIs in general, I guess)
should be moving towards the more formal style of Documentation/ABI to
help manage userspace expectations - the separation of the documentation
applies to most other things in there as well.
next prev parent reply other threads:[~2009-09-04 16:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 16:26 [PATCH 1/2] rtc: Document the sysfs interface Matthew Garrett
2009-09-04 16:26 ` [PATCH 2/2] rtc: Add boot_timesource sysfs attribute Matthew Garrett
2009-09-04 16:25 ` [rtc-linux] " Alessandro Zummo
2009-09-04 16:30 ` Matthew Garrett
2009-09-04 16:38 ` [rtc-linux] " Alessandro Zummo
2009-09-04 16:41 ` Matthew Garrett
2009-09-04 16:52 ` Alessandro Zummo
2009-09-04 16:55 ` Matthew Garrett
2009-09-04 17:03 ` Alessandro Zummo
2009-09-04 17:09 ` Matthew Garrett
2009-09-05 21:11 ` Alessandro Zummo
2009-09-06 1:34 ` Mark Brown
2009-09-14 22:59 ` Karel Zak
2009-09-04 16:26 ` [rtc-linux] [PATCH 1/2] rtc: Document the sysfs interface Alessandro Zummo
2009-09-04 16:35 ` Mark Brown
2009-09-04 16:39 ` Matthew Garrett
2009-09-04 16:52 ` Mark Brown [this message]
2009-09-04 23:23 ` [rtc-linux] " Andrew Morton
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=20090904165206.GF1576@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=a.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox