All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: David Brownell <david-b@pacbell.net>, Greg KH <greg@kroah.com>,
	linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: [BK PATCH] USB device support for 2.5.8 (take 2)
Date: Wed, 17 Apr 2002 11:08:09 -0700	[thread overview]
Message-ID: <20020417110809.R745@work.bitmover.com> (raw)
In-Reply-To: <074401c1e629$0a9ea020$6800000a@brownell.org> <Pine.LNX.4.33.0204171043260.17271-100000@home.transmeta.com>

On Wed, Apr 17, 2002 at 10:57:21AM -0700, Linus Torvalds wrote:
> Since we're talking about the other end of a "host" driver, "client" makes
> sense - in computers, I've always seen "client" as the reverse of the
> "host", but maybe that's just me. Outside of computers, "guest" seems to
> be the proper antonym, but that just strikes me as bizarre (a "USB guest
> driver"?)

What about "target"?  In SCSI land, it's clear that a target is the device,
and when you talk about code that runs on a computer and makes it be a 
SCSI target, everyone knows what you mean, right?  So what about code that
makes a computer a USB target?  Would that work?  That's the only thing I
could think of that was similar.  Does USB already use the term target for
something else?
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2002-04-17 18:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 22:54 [BK PATCH] USB device support for 2.5.8 Greg KH
2002-04-16 22:58 ` Greg KH
2002-04-17  2:51 ` [BK PATCH] USB device support for 2.5.8 (take 2) Greg KH
2002-04-17  2:53   ` Greg KH
2002-04-17  4:35   ` Linus Torvalds
2002-04-17  3:52     ` Greg KH
2002-04-17  5:08       ` Linus Torvalds
2002-04-17 13:44         ` Greg KH
2002-04-17 16:00           ` [linux-usb-devel] " David Brownell
2002-04-17 17:57             ` Linus Torvalds
2002-04-17 18:08               ` Larry McVoy [this message]
2002-04-17 18:59                 ` Linus Torvalds
2002-04-17 18:14                   ` Greg KH
2002-04-17 18:17               ` Greg KH
2002-04-19  5:37                 ` George J Karabin
2002-04-19  5:46                   ` [linux-usb-devel] Re: [BK PATCH] USB device support for 2.5.8(take 2) Oliver Neukum
2002-04-19  6:11                     ` George J Karabin
2002-04-19 11:06                       ` [linux-usb-devel] Re: [BK PATCH] USB device support for2.5.8(take2) Oliver.Neukum
2002-04-19 16:22                         ` George J Karabin
2002-04-17 18:41               ` [linux-usb-devel] Re: [BK PATCH] USB device support for 2.5.8 (take 2) Stephen J. Gowdy
2002-04-17 18:31                 ` Greg KH
2002-04-17 18:44               ` [linux-usb-devel] Re: [BK PATCH] USB device support for 2.5.8 arjan
2002-04-17 19:02               ` [linux-usb-devel] Re: [BK PATCH] USB device support for 2.5.8 (take 2) Oliver Xymoron
2002-04-17 19:20               ` David Brownell
2002-04-17 20:07                 ` Johannes Erdfelt
  -- strict thread matches above, loose matches on Subject: below --
2002-04-17 19:58 Adam_Kessler

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=20020417110809.R745@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=torvalds@transmeta.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 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.