From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nishanth Menon <nm@ti.com>, Aaron Lu <aaron.lu@intel.com>,
Jeff Garzik <jgarzik@redhat.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [GIT PULL] ACPI and power management fixes for v3.9-rc1
Date: Tue, 26 Feb 2013 08:37:12 -0800 [thread overview]
Message-ID: <20130226163712.GA30433@htj.dyndns.org> (raw)
In-Reply-To: <CA+55aFyu5woJsH2y3y=w4UFneOG8hKz_cLXgZQbJzn5asn8=hQ@mail.gmail.com>
On Tue, Feb 26, 2013 at 08:28:56AM -0800, Linus Torvalds wrote:
> > Aaron, Tejun, Jeff, can I ask you to also not use specialized TLA's
> > without explaining them? Especially in help text and "documentation",
> > it's very unhelpful to have TLA's that aren't common.
> >
> > We don't have to explain *all* TLA's, since there's a lot that really
> > are rather widespread. But there's a big difference between something
> > like CPU or TLB that have been in generic literature for decades, wrt
> > OPP and ODD that are specialized terms used inside a very particular
> > group and haven't been around for very long either.
Aye aye, captain.
One interesting bit, for me (and possibly Aaron too), ODD is much more
closer to an everyday term. For some reason, at least in Korea, ODD
is a popular term. For exmple, the likes of newegg would use it along
with CPU, SSD or VGA to label product categories, so that probably is
why ODD never registered as something which needed explanation, and
that we all are pretty familiar with ATA jargons. Anyways, yeah, no
ODDs without expansion nearby.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-02-26 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 14:29 [GIT PULL] ACPI and power management fixes for v3.9-rc1 Rafael J. Wysocki
2013-02-26 3:17 ` Rafael J. Wysocki
2013-02-26 5:31 ` Linus Torvalds
2013-02-26 15:55 ` Rafael J. Wysocki
2013-02-26 16:10 ` Nishanth Menon
2013-02-26 16:27 ` Linus Torvalds
2013-02-26 16:28 ` Linus Torvalds
2013-02-26 16:37 ` Tejun Heo [this message]
2013-02-26 16:47 ` Linus Torvalds
2013-02-26 16:58 ` Tejun Heo
2013-02-26 17:59 ` Jeff Garzik
2013-03-01 1:32 ` [PATCH] [libata] Avoid specialized TLA's in ZPODD's Kconfig Aaron Lu
2013-03-01 13:10 ` Sergei Shtylyov
2013-03-02 5:00 ` [PATCH v2] " Aaron Lu
2013-03-04 22:14 ` Jeff Garzik
2013-02-27 2:24 ` [GIT PULL] ACPI and power management fixes for v3.9-rc1 Aaron Lu
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=20130226163712.GA30433@htj.dyndns.org \
--to=tj@kernel.org \
--cc=aaron.lu@intel.com \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).