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

On Aug 10 2004, at 01:11, Alan Cox was caught saying:
> 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".
> 
> The existing format with spaces looks a lot better in all the
> graphical file managers.

Files w/o spaces look better and is easier to work with if running 
from cmd line, but if we ignore the "prettyness" issue, we should at 
least try to be consistent. Either we have spaces and _all_ driver 
names are in the format "xxx IDE", "xxx i2c", etc, or we don't allow
space at all. 

~Deepak

-- 
Deepak Saxena - dsaxena at plexity dot net - http://www.plexity.net/

"Unlike me, many of you have accepted the situation of your imprisonment and
 will die here like rotten cabbages." - Number 6

  reply	other threads:[~2004-08-10  2:12 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 [this message]
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
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=20040810021209.GA10495@plexity.net \
    --to=dsaxena@plexity.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.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 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.