From: Ralf Baechle <ralf@linux-mips.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
Wu Zhangjin <wuzhangjin@gmail.com>,
linux-mips@linux-mips.org, Thomas Gleixner <tglx@linutronix.de>,
Michal Simek <monstr@monstr.eu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MIPS: Add a high resolution sched_clock() via cnt32_to_63().
Date: Sun, 22 Nov 2009 20:23:14 +0000 [thread overview]
Message-ID: <20091122202314.GB1941@linux-mips.org> (raw)
In-Reply-To: <20091122180616.GB24711@elte.hu>
On Sun, Nov 22, 2009 at 07:06:16PM +0100, Ingo Molnar wrote:
> > MIPS's is not really a proper English. :-)
>
> AFAIK 'MIPS' is not the plural of 'MIP' (but an acronym ending with
> 'S'), hence the possessive form would be MIPS's.
MIPS Technologies' IP lawyers insist that MIPS is a proper name and not an
acronym - this position has certain advantages in trademark law.
Historically MIPS stood for Microprocessor without Interlocked Pipeline
Stages but technically may only have been true for the original Stanford
RISC processor but certainly not for the first commercial MIPS processor,
the R2000, which was released in 1985 which at least had some interlocks.
> It doesnt matter much i guess ;-)
Not to us because we're not trademark lawyers ;-)
Ralf
next prev parent reply other threads:[~2009-11-22 20:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 7:44 [PATCH v2] MIPS: Add a high resolution sched_clock() via cnt32_to_63() Wu Zhangjin
2009-11-22 8:13 ` Ingo Molnar
2009-11-22 11:08 ` Wu Zhangjin
2009-11-22 11:55 ` Sergei Shtylyov
2009-11-22 12:35 ` Ralf Baechle
2009-11-22 13:18 ` Wu Zhangjin
2009-11-22 11:51 ` Sergei Shtylyov
2009-11-22 18:06 ` Ingo Molnar
2009-11-22 20:23 ` Ralf Baechle [this message]
2009-11-23 8:42 ` Ingo Molnar
2009-12-02 1:58 ` Maciej W. Rozycki
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=20091122202314.GB1941@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mingo@elte.hu \
--cc=monstr@monstr.eu \
--cc=sshtylyov@ru.mvista.com \
--cc=tglx@linutronix.de \
--cc=wuzhangjin@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