From: Koen Kooi <koen@handhelds.org>
To: linux-kernel@vger.kernel.org, greg@kroah.com
Subject: [PATCH] correct wording in drivers/usb/net/KConfig
Date: Tue, 25 Oct 2005 14:21:54 +0200 [thread overview]
Message-ID: <435E2362.6010203@handhelds.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 726 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
drivers/usb/net/KConfig mention the word ROM ('Read Only Memory') a few
times in combination with the Sharp Zaurus family. The original software
from sharp (and clones) use cramfs as a root partition which indeed is
Read only. OpenZaurus however (and other distributions like Familiar)
use jffs2 as a filesystem for the rootfs on flash, so ROM is not the
correct term to use. Attached is a patch which removes the word 'ROM' in
the sentence mentioning OpenZaurus.
regards,
Koen Kooi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFDXiNiMkyGM64RGpERAqwOAJ94Pa3w0ww2yi0a/9bFR7oORAjm9wCgjavX
HThMWubjyE5UGRaiC/lIP78=
=1vIW
-----END PGP SIGNATURE-----
[-- Attachment #2: no-ROM.patch --]
[-- Type: text/x-patch, Size: 656 bytes --]
--- ../Kconfig 2005-10-25 14:09:29.442239520 +0200
+++ drivers/usb/net/Kconfig 2005-10-25 14:10:30.644935296 +0200
@@ -294,7 +294,7 @@
This also supports some related device firmware, as used in some
PDAs from Olympus and some cell phones from Motorola.
- If you install an alternate ROM image, such as the Linux 2.6 based
+ If you install an alternate image, such as the Linux 2.6 based
versions of OpenZaurus, you should no longer need to support this
protocol. Only the "eth-fd" or "net_fd" drivers in these devices
really need this non-conformant variant of CDC Ethernet (or in
next reply other threads:[~2005-11-01 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 12:21 Koen Kooi [this message]
2005-10-26 17:03 ` [PATCH] correct wording in drivers/usb/net/KConfig Greg KH
2005-10-26 17:42 ` Koen Kooi
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=435E2362.6010203@handhelds.org \
--to=koen@handhelds.org \
--cc=greg@kroah.com \
--cc=koen@dominion.kabel.utwente.nl \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.