From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Tom Fredrik Blenning Klaussen <bfg-kernel@blenning.no>,
linux-kernel@vger.kernel.org
Subject: [2.6 patch] firmware spelling errors
Date: Sun, 24 Oct 2004 16:13:28 +0200 [thread overview]
Message-ID: <20041024141328.GF4216@stusta.de> (raw)
The trivial patch by Tom Fredrik Blenning Klaussen below which fixes
some mis-spelings of the word "firmware" still applies against
2.6.9-mm1.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
diff -ruN /usr/src/linux-2.6.8.1/drivers/atm/fore200e.h ./drivers/atm/fore200e.h
--- /usr/src/linux-2.6.8.1/drivers/atm/fore200e.h 2004-08-31 13:11:45.000000000 +0200
+++ ./drivers/atm/fore200e.h 2004-09-12 19:47:30.000000000 +0200
@@ -645,7 +645,7 @@
typedef struct fw_header {
u32 magic; /* magic number */
- u32 version; /* firware version id */
+ u32 version; /* firmware version id */
u32 load_offset; /* fw load offset in board memory */
u32 start_offset; /* fw execution start address in board memory */
} fw_header_t;
diff -ruN /usr/src/linux-2.6.8.1/drivers/base/Kconfig ./drivers/base/Kconfig
--- /usr/src/linux-2.6.8.1/drivers/base/Kconfig 2004-08-31 13:11:45.000000000 +0200
+++ ./drivers/base/Kconfig 2004-09-12 19:47:30.000000000 +0200
@@ -14,7 +14,7 @@
default y
help
Say yes to avoid building firmware. Firmware is usually shipped
- with the driver, and only when updating the firware a rebuild
+ with the driver, and only when updating the firmware a rebuild
should be made.
If unsure say Y here.
diff -ruN /usr/src/linux-2.6.8.1/drivers/net/wan/cosa.c ./drivers/net/wan/cosa.c
--- /usr/src/linux-2.6.8.1/drivers/net/wan/cosa.c 2004-08-31 13:11:45.000000000 +0200
+++ ./drivers/net/wan/cosa.c 2004-09-12 19:47:30.000000000 +0200
@@ -156,7 +156,7 @@
unsigned short startaddr; /* Firmware start address */
unsigned short busmaster; /* Use busmastering? */
int nchannels; /* # of channels on this card */
- int driver_status; /* For communicating with firware */
+ int driver_status; /* For communicating with firmware */
int firmware_status; /* Downloaded, reseted, etc. */
long int rxbitmap, txbitmap; /* Bitmap of channels who are willing to send/receive data */
long int rxtx; /* RX or TX in progress? */
diff -ruN /usr/src/linux-2.6.8.1/drivers/scsi/megaraid.c ./drivers/scsi/megaraid.c
--- /usr/src/linux-2.6.8.1/drivers/scsi/megaraid.c 2004-08-31 13:11:45.000000000 +0200
+++ ./drivers/scsi/megaraid.c 2004-09-12 19:47:30.000000000 +0200
@@ -4006,7 +4006,7 @@
mbox->m_out.xferaddr = (u32)adapter->buf_dma_handle;
/*
- * Non-ROMB firware fail this command, so all channels
+ * Non-ROMB firmware fail this command, so all channels
* must be shown RAID
*/
adapter->mega_ch_class = 0xFF;
reply other threads:[~2004-10-24 14:14 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=20041024141328.GF4216@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=bfg-kernel@blenning.no \
--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 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).