From: Randy Dunlap <rdunlap@infradead.org>
To: Palmer Dabbelt <palmer@dabbelt.com>, georgedanielmangum@gmail.com
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, Atish Patra <Atish.Patra@wdc.com>,
peterz@infradead.org, wangkefeng.wang@huawei.com,
will@kernel.org, tglx@linutronix.de,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: cacheinfo: fix typo of homogenous
Date: Sat, 23 Oct 2021 13:36:47 -0700 [thread overview]
Message-ID: <750f6239-154d-9190-24ff-ece033add638@infradead.org> (raw)
In-Reply-To: <mhng-51275835-4c34-4099-85f5-13c6dbef4e19@palmerdabbelt-glaptop>
On 10/23/21 1:30 PM, Palmer Dabbelt wrote:
> On Fri, 08 Oct 2021 13:56:25 PDT (-0700), georgedanielmangum@gmail.com wrote:
>> Updates 'homonogenous' to 'homogenous' in comment.
>
> I don't really know spelling that well, but checkpatch says
>
> WARNING: 'homogenous' may be misspelled - perhaps 'homogeneous'?
>
> when applying this. It looks like they're both words, but "homogeneous" is the right one?
>
Internet search to grammar.com says:
To summarise, Earlier, homogenous was used as a scientific term, mainly in biology, but now it is almost obsolete, being replaced by homologous. Whereas, homogeneous is a common word, very much in use and means having similar or comparable characteristics.
Several web sites agree that homogeneous is currently preferable.
>>
>> Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
>> ---
>> arch/riscv/kernel/cacheinfo.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/riscv/kernel/cacheinfo.c b/arch/riscv/kernel/cacheinfo.c
>> index 90deabfe63ea..ff98546b1152 100644
>> --- a/arch/riscv/kernel/cacheinfo.c
>> +++ b/arch/riscv/kernel/cacheinfo.c
>> @@ -29,7 +29,7 @@ static struct cacheinfo *get_cacheinfo(u32 level, enum cache_type type)
>> /*
>> * Using raw_smp_processor_id() elides a preemptability check, but this
>> * is really indicative of a larger problem: the cacheinfo UABI assumes
>> - * that cores have a homonogenous view of the cache hierarchy. That
>> + * that cores have a homogenous view of the cache hierarchy. That
>> * happens to be the case for the current set of RISC-V systems, but
>> * likely won't be true in general. Since there's no way to provide
>> * correct information for these systems via the current UABI we're
--
~Randy
next prev parent reply other threads:[~2021-10-23 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 20:56 hasheddan
2021-10-23 20:30 ` Palmer Dabbelt
2021-10-23 20:36 ` Randy Dunlap [this message]
2021-10-25 1:12 ` Daniel Mangum
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=750f6239-154d-9190-24ff-ece033add638@infradead.org \
--to=rdunlap@infradead.org \
--cc=Atish.Patra@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=georgedanielmangum@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.com \
--cc=will@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®