All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-scsi@vger.kernel.org,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scsi_error: Fix language abuse.
Date: Fri, 08 Feb 2008 11:27:03 -0500	[thread overview]
Message-ID: <47AC82D7.2070502@compro.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0802081104370.27386@chaos.analogic.com>

linux-os (Dick Johnson) wrote:
> 
> The correct word should be "invalid," in spite of
> the fact that the SCSI committee used invalid syntax.
> 
> Alan is right. There is nothing illegal in the kernel
> and if there is, it must be removed as soon as it
> is discovered!
> 
 
il·le·gal  (-lgl)
adj.
1. Prohibited by law.
*2. Prohibited by official rules: an illegal pass in football.
*3. Unacceptable to or not performable by a computer: an illegal operation.

Mark

  reply	other threads:[~2008-02-08 16:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 15:32 [PATCH] scsi_error: Fix language abuse Alan Cox
2008-02-08 15:57 ` James Bottomley
2008-02-08 15:59   ` Alan Cox
2008-02-08 16:28     ` James Bottomley
2008-02-08 16:07   ` linux-os (Dick Johnson)
2008-02-08 16:07     ` linux-os (Dick Johnson)
2008-02-08 16:27     ` Mark Hounschell [this message]
2008-02-11 16:07       ` linux-os (Dick Johnson)
2008-02-11 16:07         ` linux-os (Dick Johnson)
2008-02-11 17:13         ` Benny Halevy
2008-02-11 17:13           ` Benny Halevy
2008-02-09  1:32 ` Douglas Gilbert
2008-02-09 13:50   ` Alan Cox
2008-02-10 23:24     ` Douglas Gilbert
2008-02-10 23:47     ` Matthew Wilcox
2008-02-09  8:02 ` Luben Tuikov

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=47AC82D7.2070502@compro.net \
    --to=markh@compro.net \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.