From: Peter Huewe <peterhuewe@gmx.de>
To: Greg KH <greg@kroah.com>
Cc: Greg KH <gregkh@suse.de>,
devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
Harry Wei <jiaweiwei.xiyou@gmail.com>,
Peter Huewe <peterhuewe@gmx.de>
Subject: [PATCH 08/27] staging/et131x: Fix common spelling mistakes
Date: Sat, 26 Mar 2011 02:39:17 +0100 [thread overview]
Message-ID: <1301103576-16109-8-git-send-email-peterhuewe@gmx.de> (raw)
This patch fixes some very common spelling mistakes in
drivers/staging/brcm80211.
WRONG -> RIGHT
accomodate -> accommodate
occured -> occurred
Kernel Version: staging/staging-next 20110325 (4bbba111)
Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
---
drivers/staging/et131x/et1310_rx.c | 2 +-
drivers/staging/et131x/et131x_isr.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/et131x/et1310_rx.c b/drivers/staging/et131x/et1310_rx.c
index 339136f..fc6bd43 100644
--- a/drivers/staging/et131x/et1310_rx.c
+++ b/drivers/staging/et131x/et1310_rx.c
@@ -122,7 +122,7 @@ int et131x_rx_dma_memory_alloc(struct et131x_adapter *adapter)
* number of entries in FBR1.
*
* FBR1 holds "large" frames, FBR0 holds "small" frames. If FBR1
- * entries are huge in order to accomodate a "jumbo" frame, then it
+ * entries are huge in order to accommodate a "jumbo" frame, then it
* will have less entries. Conversely, FBR1 will now be relied upon
* to carry more "normal" frames, thus it's entry size also increases
* and the number of entries goes up too (since it now carries
diff --git a/drivers/staging/et131x/et131x_isr.c b/drivers/staging/et131x/et131x_isr.c
index ce4d930..f716e40 100644
--- a/drivers/staging/et131x/et131x_isr.c
+++ b/drivers/staging/et131x/et131x_isr.c
@@ -466,7 +466,7 @@ void et131x_isr_handler(struct work_struct *work)
/* Handle SLV Timeout Interrupt */
if (status & ET_INTR_SLV_TIMEOUT) {
/*
- * This means a timeout has occured on a read or
+ * This means a timeout has occurred on a read or
* write request to one of the JAGCore registers. The
* Global Resources block has terminated the request
* and on a read request, returned a "fake" value.
--
1.7.3.4
next reply other threads:[~2011-03-26 1:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 1:39 Peter Huewe [this message]
2011-03-26 1:39 ` [PATCH 09/27] staging/ft1000: " Peter Huewe
2011-03-26 1:39 ` [PATCH 10/27] staging/iio: " Peter Huewe
2011-03-26 1:39 ` [PATCH 11/27] staging/intel_sst: " Peter Huewe
2011-03-26 1:39 ` [PATCH 12/27] staging/lirc: " Peter Huewe
2011-03-26 1:39 ` [PATCH 13/27] staging/octeon: " Peter Huewe
2011-03-26 1:39 ` [PATCH 14/27] staging/olpc_dcon: " Peter Huewe
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=1301103576-16109-8-git-send-email-peterhuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=devel@linuxdriverproject.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=jiaweiwei.xiyou@gmail.com \
--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
all inboxes | Powered by JetHome®