From: Hirokazu Nomoto <hng@ps.ksky.ne.jp>
To: Alan.Cox@linux.org, torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org, hng@ps.ksky.ne.jp
Subject: SubmittingDrivers of Linux kernel Documentation
Date: Wed, 12 Dec 2001 02:03:18 +0900 [thread overview]
Message-ID: <20011212020318D.hng@ps.ksky.ne.jp> (raw)
Hello.
I think there is some typo about SubmittingDrivers of Linux kernel
Documentation.
So, I made a patch for 2.2.20 and 2.4.16.
Please apply them.
I don't know this maintainer or autor, so I send you.
regards,
Hiro
For 2.2.20:
======================================================================
--- SubmittingDrivers Sat Nov 3 01:39:05 2001
+++ SubmittingDrivers.new Wed Dec 12 01:50:00 2001
@@ -14,7 +14,7 @@
site is http://www.lanana.org/. This also deals with allocating numbers for
devices that are not going to be submitted to the mainstream kernel.
-If you don't use assigned numbers then when you device is submitted it will
+If you don't use assigned numbers then when your device is submitted it will
get given an assigned number even if that is different from values you may
have shipped to customers before.
@@ -57,7 +57,7 @@
in Documentation/CodingStyle. If you have sections of code
that need to be in other formats, for example because they
are shared with a windows driver kit and you want to
- maintain them just once seperate them out nicely and note
+ maintain them just once separate them out nicely and note
this fact.
Portability: Pointers are not always 32bits, people do not all have
======================================================================
For 2.4.16:
======================================================================
--- SubmittingDrivers Tue Aug 28 00:59:16 2001
+++ SubmittingDrivers.new Wed Dec 12 01:52:47 2001
@@ -18,7 +18,7 @@
also deals with allocating numbers for devices that are not going to
be submitted to the mainstream kernel.
-If you don't use assigned numbers then when you device is submitted it will
+If you don't use assigned numbers then when your device is submitted it will
get given an assigned number even if that is different from values you may
have shipped to customers before.
@@ -61,7 +61,7 @@
in Documentation/CodingStyle. If you have sections of code
that need to be in other formats, for example because they
are shared with a windows driver kit and you want to
- maintain them just once seperate them out nicely and note
+ maintain them just once separate them out nicely and note
this fact.
Portability: Pointers are not always 32bits, people do not all have
======================================================================
reply other threads:[~2001-12-11 17:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011212020318D.hng@ps.ksky.ne.jp \
--to=hng@ps.ksky.ne.jp \
--cc=Alan.Cox@linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).