public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Frank Lee <tiny.windzz@gmail.com>, peda@axentia.se
Cc: linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] i2c: rk3x: fix some typo
Date: Tue, 06 Nov 2018 13:01:33 +0100	[thread overview]
Message-ID: <12637568.SqdzpTGmKQ@phil> (raw)
In-Reply-To: <CAEExFWtQrPD8hUn15Add-EuueCL5=Crb+yvDckWejG75BExGug@mail.gmail.com>

Hi Yangtao, Peter,

Am Montag, 5. November 2018, 16:59:58 CET schrieb Frank Lee:
> I am sorry.
> -- Yangtao

If anything, it is me that should be sorry, as I did suggest the
patch description, including the new spelling error.

And it took me like the whole weekend to actually realize where the
Calculated / Calculates error was hiding ;-) .


Heiko

> On Fri, Nov 2, 2018 at 8:58 PM Peter Rosin <peda@axentia.se> wrote:
> >
> > On 2018-11-02 13:45, Yangtao Li wrote:
> > > Fix multiple instances of a misspelled "Calculates".
> >
> > Yes, it sure is hard to spell "Calcluated," it's almost impossible to
> > get it completely right and not introduce another typo somewhere... :-)
> >
> > Cheers,
> > Peter
> >
> > >
> > > Signed-off-by: Yangtao Li <tiny.windzz@gmail.com>
> > > Reviewed-by: Heiko Stuebner <heiko@sntech.de>
> > > ---
> > > Changes in v2:
> > > -add commit message
> > > ---
> > >  drivers/i2c/busses/i2c-rk3x.c | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/i2c/busses/i2c-rk3x.c b/drivers/i2c/busses/i2c-rk3x.c
> > > index b8a2728dd4b6..fe347e8e2a23 100644
> > > --- a/drivers/i2c/busses/i2c-rk3x.c
> > > +++ b/drivers/i2c/busses/i2c-rk3x.c
> > > @@ -555,7 +555,7 @@ static const struct i2c_spec_values *rk3x_i2c_get_spec(unsigned int speed)
> > >   *
> > >   * @clk_rate: I2C input clock rate
> > >   * @t: Known I2C timing information
> > > - * @t_calc: Caculated rk3x private timings that would be written into regs
> > > + * @t_calc: Calculated rk3x private timings that would be written into regs
> > >   *
> > >   * Returns: 0 on success, -EINVAL if the goal SCL rate is too slow. In that case
> > >   * a best-effort divider value is returned in divs. If the target rate is
> > > @@ -716,7 +716,7 @@ static int rk3x_i2c_v0_calc_timings(unsigned long clk_rate,
> > >   *
> > >   * @clk_rate: I2C input clock rate
> > >   * @t: Known I2C timing information
> > > - * @t_calc: Caculated rk3x private timings that would be written into regs
> > > + * @t_calc: Calculated rk3x private timings that would be written into regs
> > >   *
> > >   * Returns: 0 on success, -EINVAL if the goal SCL rate is too slow. In that case
> > >   * a best-effort divider value is returned in divs. If the target rate is
> > >
> >
> 





  reply	other threads:[~2018-11-06 12:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 12:45 [PATCH v2] i2c: rk3x: fix some typo Yangtao Li
2018-11-02 12:58 ` Peter Rosin
2018-11-05 15:59   ` Frank Lee
2018-11-06 12:01     ` Heiko Stuebner [this message]
2018-11-06 13:01       ` Frank Lee
2018-11-06 13:02         ` Frank Lee
2018-11-09 16:09       ` Wolfram Sang

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=12637568.SqdzpTGmKQ@phil \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=peda@axentia.se \
    --cc=tiny.windzz@gmail.com \
    /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