From: Grant Likely <grant.likely@secretlab.ca>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: trivial@kernel.org, linux-kernel@vger.kernel.org,
spi-devel-general@lists.sourceforge.net
Subject: Re: [PATCH] spi/spi_topcliff_pch.c Typo change threhold to threshold
Date: Fri, 31 Dec 2010 17:49:44 -0700 [thread overview]
Message-ID: <20110101004944.GC19643@angua.secretlab.ca> (raw)
In-Reply-To: <1293817831-8263-1-git-send-email-justinmattock@gmail.com>
On Fri, Dec 31, 2010 at 09:50:31AM -0800, Justin P. Mattock wrote:
> The below patch changes a typo from "threhold" to "threshold".
> Let me know if I missed anything.
>
> Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
Applied, thanks.
g.
>
> ---
> drivers/spi/spi_topcliff_pch.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/spi/spi_topcliff_pch.c b/drivers/spi/spi_topcliff_pch.c
> index 58e187f..be451e3 100644
> --- a/drivers/spi/spi_topcliff_pch.c
> +++ b/drivers/spi/spi_topcliff_pch.c
> @@ -677,7 +677,7 @@ static void pch_spi_set_ir(struct pch_spi_data *data)
> {
> /* enable interrupts */
> if ((data->bpw_len) > PCH_MAX_FIFO_DEPTH) {
> - /* set receive threhold to PCH_RX_THOLD */
> + /* set receive threshold to PCH_RX_THOLD */
> pch_spi_setclr_reg(data->master, PCH_SPCR,
> PCH_RX_THOLD << SPCR_TFIC_FIELD,
> ~MASK_TFIC_SPCR_BITS);
> @@ -685,7 +685,7 @@ static void pch_spi_set_ir(struct pch_spi_data *data)
> pch_spi_setclr_reg(data->master, PCH_SPCR,
> SPCR_RFIE_BIT | SPCR_TFIE_BIT, 0);
> } else {
> - /* set receive threhold to maximum */
> + /* set receive threshold to maximum */
> pch_spi_setclr_reg(data->master, PCH_SPCR,
> PCH_RX_THOLD_MAX << SPCR_TFIC_FIELD,
> ~MASK_TFIC_SPCR_BITS);
> --
> 1.6.5.2.180.gc5b3e
>
prev parent reply other threads:[~2011-01-01 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 17:50 [PATCH] spi/spi_topcliff_pch.c Typo change threhold to threshold Justin P. Mattock
2011-01-01 0:49 ` Grant Likely [this message]
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=20110101004944.GC19643@angua.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=trivial@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).