[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 3 Mar 2008 11:20:55 +0100
From: "Michael Kerrisk" <mtk.manpages@...glemail.com>
To: "Ingo Molnar" <mingo@...e.hu>
Cc: "Arnd Bergmann" <arnd@...db.de>, "Christoph Hellwig" <hch@....de>,
cbe-oss-dev@...abs.org, "Jeremy Kerr" <jk@...abs.org>,
linux-kernel@...r.kernel.org,
"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: SCHED_IDLE documentation
On Mon, Mar 3, 2008 at 11:17 AM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * Michael Kerrisk <mtk.manpages@...glemail.com> wrote:
>
>
> > > commit 0e6aca43e08a62a48d6770e9a159dbec167bf4c6
> > > Author: Ingo Molnar <mingo@...e.hu>
> > > Date: Mon Jul 9 18:51:57 2007 +0200
> >
> > Yep -- I found it later -- thanks.
> >
> > Ingo, could you please CC me when kernel-userland API changes go into
> > mainline? Otherwise, they potentially end up undocumented, and
> > un(der)used.
>
> sure.
>
> We could also add an in-commit-message marker for such changes, that you
> could periodically scan. Something like:
>
> User-ABI-extended-by: Ingo Molnar <mingo@...e.hu>
>
> and:
>
> User-ABI-modified-by: Ingo Molnar <mingo@...e.hu>
>
> that way you also know whom to contact about followup questions.
>
> Declaring such changes would have other benefits as well: the review
> process becomes more streamlined. Also, any ABI side-effect would be
> known to be intentional versus unintentional, based on the commit
> headers alone. Undeclared ABI side-effects would be frowned upon and
> would be strong grounds for immediate reversal as well.
Sounds like an excellent idea, if we could make it fly. How can we make it fly?
Cheers,
Michael
--
Michael Kerrisk
Maintainer of the Linux man-pages project
http://www.kernel.org/doc/man-pages/
Want to report a man-pages bug? Look here:
http://www.kernel.org/doc/man-pages/reporting_bugs.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists