All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] sna: Correct misspelled cacheing->caching in comments
Date: Thu, 2 Jul 2015 09:26:11 +0200	[thread overview]
Message-ID: <CA+icZUW_pTkt_7DYwJY_fOuJgK2QCzCcd1XAfT-WLpk46==m-w@mail.gmail.com> (raw)
In-Reply-To: <20150624100443.GG12403@nuc-i3427.alporthouse.com>

On Wed, Jun 24, 2015 at 12:04 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Tue, Jun 23, 2015 at 07:45:42AM +0200, Sedat Dilek wrote:
>> I have seen this typo once and added an entry to codespell's dictionary.txt file.
>>
>> $ diff -uprN /usr/share/codespell/dictionary.txt.orig /usr/share/codespell/dictionary.txt
>> --- /usr/share/codespell/dictionary.txt.orig    2015-06-09 20:49:25.000000000 +0200
>> +++ /usr/share/codespell/dictionary.txt 2015-06-23 07:37:35.893689539 +0200
>> @@ -625,6 +625,7 @@ burried->buried
>>  busineses->business, businesses,
>>  busness->business
>>  bussiness->business
>> +cacheing->caching
>>  caculater->calculator
>>  cacuses->caucuses
>>  cahracters->characters
>>
>> There some other places where this typo occurs:
>>
>> [ src/sna/kgem.c ]
>>
>>  298:static void assert_cacheing(struct kgem *kgem, struct kgem_bo *bo)
>>  324:#define assert_cacheing(kgem, bo)
>> 2455:  assert_cacheing(kgem, bo);
>> 2841:  assert_cacheing(kgem, bo);
>>
>> It's up to Chris what to do with this.
>
> I just can't get paste reading 'caching' as two hard Cs and so it feels
> weird.
>
> commit f414ed4e40292e91e9c6850fb01a26334e6b43c7
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Wed Jun 24 11:02:28 2015 +0100
>
>     sna: Fix misspelling of "caching"
>
>     Apply s/cacheing/caching/ because I am alone in my belief of how to
>     spell cacheing correctly :)
>
>     Suggested-by: Sedat Dilek <sedat.dilek@gmail.com>
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>

Thanks.

Just FYI... codespell got it, now.

commit b003c6167fdf441d2ba89534d402015723b66560
"Add misspelled cacheing->caching"

- sed@ -

[1] https://github.com/lucasdemarchi/codespell/commit/b003c6167fdf441d2ba89534d402015723b66560
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2015-07-02  7:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23  5:45 [PATCH] sna: Correct misspelled cacheing->caching in comments Sedat Dilek
2015-06-24 10:04 ` Chris Wilson
2015-06-26 14:51   ` Dave Gordon
2015-07-02  7:26   ` Sedat Dilek [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='CA+icZUW_pTkt_7DYwJY_fOuJgK2QCzCcd1XAfT-WLpk46==m-w@mail.gmail.com' \
    --to=sedat.dilek@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.