All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dsaxena@plexity.net,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6] Remove spaces from PCI IDE pci_driver.name field
Date: Tue, 10 Aug 2004 09:40:31 -0700	[thread overview]
Message-ID: <20040810164031.GB31655@kroah.com> (raw)
In-Reply-To: <1092096699.14934.4.camel@localhost.localdomain>

On Tue, Aug 10, 2004 at 01:11:42AM +0100, Alan Cox wrote:
> On Maw, 2004-08-10 at 01:13, Deepak Saxena wrote:
> > Spaces in driver names show up as spaces in sysfs. Annoying.  
> > I went ahead and changed ones that don't have spaces to use
> > ${NAME}_IDE so they are all consistent.
> 
> I don't see the problem with spaces in the filenames. I do see the 
> problem in changing stuff under people for now reason other than
> "I don't like it".

We tried to keep spaces out of device and driver names from the very
beginning, in 2.5 during the conversion to the driver model, due to the
confusion it caused people.  It seems that a few have snuck back in.
I'm all for consistancy, so I'll apply these patches.

thanks,

greg k-h

  parent reply	other threads:[~2004-08-10 18:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  0:13 [PATCH 2.6] Remove spaces from PCI IDE pci_driver.name field Deepak Saxena
2004-08-10  0:11 ` Alan Cox
2004-08-10  2:12   ` Deepak Saxena
2004-08-10 11:52     ` Alan Cox
2004-08-10 15:57       ` Tomas Szepe
2004-08-10 16:13         ` Lee Revell
2004-08-10 16:18           ` Tomas Szepe
2004-08-10 16:52           ` V13
2004-08-10 16:55             ` Lee Revell
2004-08-10 16:57               ` Tomas Szepe
2004-08-10 17:00                 ` Lee Revell
2004-08-10 16:40   ` Greg KH [this message]
2004-08-10 23:41 ` Greg KH

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=20040810164031.GB31655@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dsaxena@plexity.net \
    --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 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.