From: Andi Kleen <ak@suse.de>
To: Anton Blanchard <anton@samba.org>
Cc: "Dugger, Donald D" <donald.d.dugger@intel.com>,
Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, "Shah,
Rajesh" <rajesh.shah@intel.com>,
akpm@osdl.org
Subject: Re: [PATCH] Add VT flag to cpuinfo
Date: Thu, 1 Dec 2005 18:57:42 +0100 [thread overview]
Message-ID: <20051201175742.GN19515@wotan.suse.de> (raw)
In-Reply-To: <20051201165205.GB12616@krispykreme>
On Fri, Dec 02, 2005 at 03:52:05AM +1100, Anton Blanchard wrote:
>
> > Well, I really don't see a conflict here, TLA's for x86
> > architectures are orthogonal to PowerPC and vice versa
> > so this shouldn't cause any confusion.
>
> Do you read all of the linux-kernel mailing list? :) Its caused me to
> have to look twice on a number of occasions.
>
> I know it isnt going to be fixed but I do wonder if intel knows how to
> use google before creating yet another TLA :)
It would be probably hopeless at least in the 2-6 letter TLA space.
Every possible TLA has been already used for countless other things.
Just live with the collisions. Or use names instead of them.
cpuinfo flags are deeply architecture specific anyways, so I don't
think it makes much sense to try to get them unique over architectures.
In fact I think ppc doesn't even have a "flags" line.
-Andi
next prev parent reply other threads:[~2005-12-01 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 16:45 Dugger, Donald D
2005-12-01 16:52 ` Anton Blanchard
2005-12-01 17:57 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-01 0:08 Dugger, Donald D
2005-11-30 23:46 Dugger, Donald D
2005-11-30 23:50 ` Andi Kleen
2005-11-30 23:34 Dugger, Donald D
2005-11-30 23:41 ` Andi Kleen
2005-12-01 16:09 ` Anton Blanchard
2005-11-30 21:17 Donald D Dugger
2005-12-01 1:52 ` Andi Kleen
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=20051201175742.GN19515@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=donald.d.dugger@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rajesh.shah@intel.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
all inboxes | Powered by JetHome®