mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Len Brown <len.brown@intel.com>
Cc: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Natalie Protasevich <Natalie.Protasevich@UNISYS.com>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: [PATCH] fix  platform_rename_gsi related ia32 build breakage
Date: Thu, 11 Nov 2004 16:01:54 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0411111552030.2301@ppc970.osdl.org> (raw)
In-Reply-To: <1100215538.5876.779.camel@d845pe>



On Thu, 11 Nov 2004, Len Brown wrote:
> 
> The _gsi in platform_rename_gsi was consistent with the surrounding use
> in the ACPI case.  I decided to re-use the same funtion for the MPS case
> for simplicity, even though io_apic.c uses _irq.  If you like, I can add
> a synonym using an inline for _irq, but I thought we were moving away
> from using _irq, not towards it.

We _definitely_ prefer "irq" over something else that means the same 
thing.

If GSI means some _specific_ interrupt, and thus has additional meaning 
over "irq", then by all means, use it, but spell it out. "Global System 
Interrupt" means _nothing_ to me. What makes it "global"? What makes it 
"system"?

The _only_ thing that uses "gsi" is the MP table stuff, and that's 
apparently just from the documentation.

In other words, if it's a normal interrupt, it's "irq" or "interrupt". The 
same way a "disk" is a "disk" - it's not a DASD. 

Stupid acronyms that don't actually mean anything more than the standard 
name are nothing but stupid.

Interrupts are interrupts. We call them something else only if they are 
_specific_ interrupts (ie a "NMI" clearly has a very _specific_ meaning, 
as has "SCI", although the latter is already obscure enough that it's 
probably a good idea to spell it out a bit if it is ever used outside of a 
context where use is obvious).

		Linus

  reply	other threads:[~2004-11-12  0:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-10 23:50 Arnaldo Carvalho de Melo
2004-11-10 23:52 ` Arnaldo Carvalho de Melo
2004-11-11  0:10   ` Arnaldo Carvalho de Melo
2004-11-11  0:18     ` Arnaldo Carvalho de Melo
2004-11-11  0:24     ` Linus Torvalds
2004-11-11  0:29       ` Arnaldo Carvalho de Melo
2004-11-11 22:22       ` Len Brown
2004-11-11 22:30         ` Linus Torvalds
2004-11-11 23:25           ` Len Brown
2004-11-12  0:01             ` Linus Torvalds [this message]
2004-11-12  2:50               ` Len Brown
2004-11-12  3:08                 ` Linus Torvalds
2004-11-11  0:20 ` Linus Torvalds
2004-11-11  0:23   ` Arnaldo Carvalho de Melo
2004-11-11  0:38 ` Andrew Morton

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=Pine.LNX.4.58.0411111552030.2301@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=Natalie.Protasevich@UNISYS.com \
    --cc=acme@conectiva.com.br \
    --cc=bjorn.helgaas@hp.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.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®