public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: Greg KH <greg@kroah.com>
Cc: Dirk DeSchepper <ddeschepper@nvtl.com>,
	USB development list <linux-usb@vger.kernel.org>,
	smurf@smurf.noris.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 001/001]  usbserial: New mobile broadband modems to be supported through option module
Date: Sat, 7 Feb 2009 10:03:34 +0100	[thread overview]
Message-ID: <200902071003.35856.oliver@neukum.org> (raw)
In-Reply-To: <20090206234716.GB31059@kroah.com>

Am Saturday 07 February 2009 00:47:16 schrieb Greg KH:

> > The specifity is not affected at all.
> 
> If you look at the names that were changed, they are now more
> descriptive than before, always a good thing to have.

They are not descriptive. As far as USB devices have names,
these names _are_ the numbers. You will be very hard pressed
to guess from a name on a box that you may or may not have
which OEM's hardware really is in that box. If you have IDs
everything is clear. People who look at this code will mostly
have bug reports which will hopefully include lsusb, but not the
symbolic name in the kernel.

We dont do
*(base + 8) = 0xb3;
here. That would be bad. We use a clearly defined macro, USB_DEVICE
which takes id _numbers_. Device IDs have no meaning. They are meant
to be unique. You can give sensible names only to things that have meaning.

This is like doing
u8 init_string1[] = { INIT_STRING1_BYTE0, INIT_STRING1_BYTE1, ...

Don't make a fetish out of symbolic names.

	Regards
		Oliver

PS: Yes, I've had a professor who did prefer it this way.


  reply	other threads:[~2009-02-07  9:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <12047829252365@kroah.org>
     [not found] ` <B29F014DE7B1F949B0BC4C1EBCF29DD6C6D1E0@Vectra.nvtl.local>
     [not found]   ` <20090206003352.GA22530@kroah.com>
2009-02-06 11:29     ` [PATCH 001/001] usbserial: New mobile broadband modems to be supported through option module Dirk DeSchepper
2009-02-06 11:58       ` Oliver Neukum
2009-02-06 18:51         ` Greg KH
2009-02-06 19:23           ` Oliver Neukum
2009-02-06 23:47             ` Greg KH
2009-02-07  9:03               ` Oliver Neukum [this message]
2009-02-06 18:52       ` Greg KH
2009-02-06 20:48         ` [PATCH 001/001] usbserial: New mobile broadband modems to besupported " Dirk DeSchepper
2009-02-07  1:11           ` patch usb-option-new-mobile-broadband-modems-to-be-supported.patch added to gregkh-2.6 tree gregkh

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=200902071003.35856.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=ddeschepper@nvtl.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=smurf@smurf.noris.de \
    /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