From: Dave Gordon <david.s.gordon@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] sna: Correct misspelled cacheing->caching in comments
Date: Fri, 26 Jun 2015 15:51:05 +0100 [thread overview]
Message-ID: <558D66D9.4090202@intel.com> (raw)
In-Reply-To: <20150624100443.GG12403@nuc-i3427.alporthouse.com>
On 24/06/15 11:04, Chris Wilson 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 past reading 'caching' as two hard Cs and so it feels
> weird.
That would be Italian. Cache (and "cachet") come from French "cacher"
(to hide), so the "ch" is (almost) the same as in "chef" or "chauffeur".
We could switch to using the Esperanto spelling, "kaŝi" and the
corresponding hardware term "kaŝmemoro" :)
.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-06-26 14:51 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 [this message]
2015-07-02 7:26 ` Sedat Dilek
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=558D66D9.4090202@intel.com \
--to=david.s.gordon@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox