From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Ralf Baechle <ralf@linux-mips.org>,
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: Wed, 2 Dec 2009 01:58:23 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.00.0912020148200.23935@eddie.linux-mips.org> (raw)
In-Reply-To: <20091123084241.GA23635@elte.hu>
On Mon, 23 Nov 2009, 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.
>
> That too seems to support my point that "MIPS's" is the right spelling.
My understanding is that "MIPS" is actually meant (as far as IP law is
concerned) to be an adjective, so you can't really make a possessive form
out of it as it is irrelevant. The correct form IMHO is thus simply:
"MIPS sched_clock implementation" which happens to sound the best to me
too.
Maciej
prev parent reply other threads:[~2009-12-02 1:58 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
2009-11-23 8:42 ` Ingo Molnar
2009-12-02 1:58 ` Maciej W. Rozycki [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=alpine.LFD.2.00.0912020148200.23935@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mingo@elte.hu \
--cc=monstr@monstr.eu \
--cc=ralf@linux-mips.org \
--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