mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 05/27] staging/crystalhd: Fix common spelling mistakes
Date: Sat, 26 Mar 2011 02:17:54 +0100	[thread overview]
Message-ID: <1301102296-15565-6-git-send-email-peterhuewe@gmx.de> (raw)
In-Reply-To: <20110314224746.GA21100@kroah.com>

This patch fixes a common spelling mistake in
drivers/staging/crystalhd.

WRONG -> RIGHT
accomodate  -> accommodate

Kernel Version: staging/staging-next 20110325 (4bbba111)

Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
---
 drivers/staging/crystalhd/crystalhd_hw.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/staging/crystalhd/crystalhd_hw.c b/drivers/staging/crystalhd/crystalhd_hw.c
index 13a514d..0faa284 100644
--- a/drivers/staging/crystalhd/crystalhd_hw.c
+++ b/drivers/staging/crystalhd/crystalhd_hw.c
@@ -2367,7 +2367,7 @@ enum BC_STATUS crystalhd_hw_set_core_clock(struct crystalhd_hw *hw)
 	BCMLOG(BCMLOG_INFO, "clock is moving to %d with n %d with vco_mg %d\n",
 	       hw->core_clock_mhz, n, vco_mg);
 
-	/* Change the DRAM refresh rate to accomodate the new frequency */
+	/* Change the DRAM refresh rate to accommodate the new frequency */
 	/* refresh reg = ((refresh_rate * clock_rate)/16) - 1; rounding up*/
 	refresh_reg = (7 * hw->core_clock_mhz / 16);
 	bc_dec_reg_wr(hw->adp, SDRAM_REF_PARAM, ((1 << 12) | refresh_reg));
-- 
1.7.3.4


  parent reply	other threads:[~2011-03-26  1:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 13:18 [PATCH] trivial: fix " Peter Huewe
2011-01-06 14:01 ` Jesper Juhl
2011-01-06 14:14   ` Peter Hüwe
2011-01-07 10:04 ` Jiri Kosina
2011-01-07 13:38   ` Peter Hüwe
2011-03-08 22:49   ` [PATCH v2/resend] " Peter Huewe
2011-03-14 12:00     ` Jiri Kosina
2011-03-14 20:35       ` [PATCH v3] " Peter Huewe
2011-03-14 21:57       ` [PATCH] staging/trivial: Fix " Peter Huewe
2011-03-14 22:03         ` Greg KH
2011-03-14 22:43           ` Peter Hüwe
2011-03-14 22:47             ` Greg KH
2011-03-26  1:17               ` [PATCH 0/27] " Peter Huewe
2011-03-26  1:17               ` [PATCH 01/27] staging/ath6kl: " Peter Huewe
2011-03-26  1:17               ` [PATCH 02/27] staging/bcm: " Peter Huewe
2011-03-26  1:17               ` [PATCH 03/27] staging/brcm80211: " Peter Huewe
2011-03-26  1:17               ` [PATCH 04/27] staging/comedi: " Peter Huewe
2011-03-26  1:17               ` Peter Huewe [this message]
2011-03-26  1:17               ` [PATCH 06/27] staging/dt3155v4l: " Peter Huewe
2011-03-26  1:17               ` [PATCH 07/27] staging/easycap: " Peter Huewe
2011-03-15  3:14         ` [PATCH] staging/trivial: " Harry Wei
2011-03-26  1:39           ` Peter Hüwe
2011-03-26  2:21             ` Harry Wei
2011-03-15  2:58     ` [PATCH v2/resend] trivial: fix " Harry Wei

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=1301102296-15565-6-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®