From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@ucw.cz>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH -mm] PM: add /sys/power documentation to Documentation/ABI
Date: Wed, 30 Aug 2006 15:51:07 -0700 [thread overview]
Message-ID: <20060830225107.GA14946@kroah.com> (raw)
In-Reply-To: <20060830153242.c5081692.akpm@osdl.org>
On Wed, Aug 30, 2006 at 03:32:42PM -0700, Andrew Morton wrote:
>
> This ABI/ thing rather snuck under my radar (I saw it go past, but a lot of
> things go past).
It had a lot of review the first time around. The second and third had
relatively little.
> It'll be good if it works, but it is going to take quite a lot of thought,
> effort and maintainer vigilance to be successful and to avoid becoming
> rotware.
I agree.
> I wonder how hard it would be to write a script which parses a diff, works
> out if it touches ABI things, complain if it doesn't alter
> Documentation/ABI/*? Not very - it's just a matter of defining a suitable
> regexp.
That would be good to have.
> What _should_ be documented in there, anyway?
>
> - syscalls, obviously.
>
> - /proc? If so, everything, or are there exceptions?
>
> - /sys? If so, everything, or are there exceptions?
>
> - ioctl numbers and payloads?
>
> - netlink messages?
>
> - ethtool thingies? netdev interface names? /proc/iomem identifiers?
> module names? kernel-thread comm[] contents? The ABI is pretty fat.
>
> scary.
Yes, our ABI is scary. And yes, all of the above is needed to be
documented if we want to have a handle on this thing.
It is probably something that we can throw at the janitors list for the
existing stuff to get some help.
thanks,
greg k-h
next prev parent reply other threads:[~2006-08-30 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 21:38 [RFC][PATCH -mm] PM: add /sys/power documentation to Documentation/ABI Rafael J. Wysocki
2006-08-30 21:35 ` Pavel Machek
2006-08-30 21:43 ` Andrew Morton
2006-08-30 22:03 ` Randy.Dunlap
2006-08-30 22:32 ` Andrew Morton
2006-08-30 22:51 ` Greg KH [this message]
2006-08-30 22:04 ` Pavel Machek
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=20060830225107.GA14946@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rdunlap@xenotime.net \
--cc=rjw@sisk.pl \
/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