Date:	Sat, 2 Feb 2008 16:22:49 -0800
From:	Greg KH <greg@...ah.com>
To:	Heikki Orsila <shdl@...alwe.fi>
Cc:	linux-kernel@...r.kernel.org, mpm@...enic.com, ak@...e.de,
	m-ikeda@...jp.nec.com, zhongyu@...ail.cn, minchan.kim@...il.com
Subject: Re: [PATCH] Improve Documentation/stable_api_nonsense.txt v2

On Sat, Feb 02, 2008 at 04:44:57PM +0200, Heikki Orsila wrote:
> This is version 2 of the patch. Address Gregs, Matts and Andis comments.
> Retain the word "exact" due to request of Greg. Use "the exact
> same" as per "Matt Mackall".
> 
> * Change wording
> * Make a remark about necessary changes in interfaces
> 
> Signed-off-by: Heikki Orsila <heikki.orsila@....fi>
> ---
>  Documentation/stable_api_nonsense.txt |   10 +++++++---
>  1 files changed, 7 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/stable_api_nonsense.txt b/Documentation/stable_api_nonsense.txt
> index 847b342..a7c29ad 100644
> --- a/Documentation/stable_api_nonsense.txt
> +++ b/Documentation/stable_api_nonsense.txt
> @@ -19,7 +19,7 @@ Executive Summary
>  You think you want a stable kernel interface, but you really do not, and
>  you don't even know it.  What you want is a stable running driver, and
>  you get that only if your driver is in the main kernel tree.  You also
> -get lots of other good benefits if your driver is in the main kernel
> +get lots of other benefits if your driver is in the main kernel
>  tree, all of which has made Linux into such a strong, stable, and mature
>  operating system which is the reason you are using it in the first
>  place.

That's fine.

> @@ -69,7 +69,7 @@ consider the following facts about the Linux kernel:
>      on another architecture properly.
>  
>  Now a number of these issues can be addressed by simply compiling your
> -module for the exact specific kernel configuration, using the same exact
> +module for the exact same kernel configuration, using the exact same
>  C compiler that the kernel was built with.  This is sufficient if you
>  want to provide a module for a specific release version of a specific
>  Linux distribution.  But multiply that single build by the number of

fine.

> @@ -116,7 +116,7 @@ issues:
>  
>  This is in stark contrast to a number of closed source operating systems
>  which have had to maintain their older USB interfaces over time.  This
> -provides the ability for new developers to accidentally use the old
> +has the risk for new developers to accidentally use the old
>  interfaces and do things in improper ways, causing the stability of the
>  operating system to suffer.
>  

fine.

> @@ -145,6 +145,10 @@ as small as possible, and that all potential interfaces are tested as
>  well as they can be (unused interfaces are pretty much impossible to
>  test for validity.)
>  
> +However, changing an interface can be delicate work and it can take
> +significant amount of developer effort. Therefore, an interface is
> +not changed unless the change is regarded as very important by the
> +developers.
>  
>  What to do
>  ----------

I still don't understand why you want to add these sentances.  Why are
they needed?  Are people thinking that the kernel developers just
randomly change things just because they are bored and have nothing else
to do at the moment?  Do people think that our changes are gratuitous?

Even so, I don't think this needs to be added, we have already stated
many good reasons why changing apis are necessary and good.  Do need to
add another one?

thanks,

greg k-h
--
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