diff options
author | Greg Kroah-Hartman <greg@kroah.com> | 2004-12-14 18:51:58 -0800 |
---|---|---|
committer | Greg Kroah-Hartman <greg@kroah.com> | 2004-12-14 18:51:58 -0800 |
commit | 145c92ecd3d205c648c44cae5d8466497962b239 (patch) | |
tree | 938fcaa7c57766092c050d944de61564119154d7 /Documentation | |
parent | 2957bf8bfeedfdf42052ab131baf1422dd0ac024 (diff) | |
download | history-145c92ecd3d205c648c44cae5d8466497962b239.tar.gz |
Documentation: fix some grammer in the stable_api_nonsense.txt file
Thanks to Andries Brouwer <aebr@win.tue.nl> for pointing this out.
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/stable_api_nonsense.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/stable_api_nonsense.txt b/Documentation/stable_api_nonsense.txt index c33c99c5100ccc..3cea1387527785 100644 --- a/Documentation/stable_api_nonsense.txt +++ b/Documentation/stable_api_nonsense.txt @@ -9,7 +9,7 @@ realize that this article describes the _in kernel_ interfaces, not the kernel to userspace interfaces. The kernel to userspace interface is the one that application programs use, the syscall interface. That interface is _very_ stable over time, and will not break. I have old -programs that were built on a pre 0.9something kernel that still works +programs that were built on a pre 0.9something kernel that still work just fine on the latest 2.6 kernel release. This interface is the one that users and application programmers can count on being stable. @@ -167,7 +167,7 @@ up by the person who did the kernel change in the first place. This ensures that your driver is always buildable, and works over time, with very little effort on your part. -The very good side affects of having your driver in the main kernel tree +The very good side effects of having your driver in the main kernel tree are: - The quality of the driver will rise as the maintenance costs (to the original developer) will decrease. |