All of lore.kernel.org
 help / color / mirror / Atom feed
From: Deepak Saxena <dsaxena@plexity.net>
To: dwmw2@infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 2.6] Remove spaces from MTD pci_driver.name field
Date: Mon, 9 Aug 2004 21:37:10 -0700	[thread overview]
Message-ID: <20040810043710.GA11719@plexity.net> (raw)


David,

Spaces in driver names show up as spaces in the sysfs tree.
While there is no documented requirement that spaces not
exist in sysfs paths, my understanding is that they are not 
desired.

Please apply,
~Deepak

Signed-off-by: Deepak Saxena <dsaxena@plexity.net>


===== drivers/mtd/maps/pci.c 1.6 vs edited =====
--- 1.6/drivers/mtd/maps/pci.c	Thu Jul 15 10:31:48 2004
+++ edited/drivers/mtd/maps/pci.c	Mon Aug  9 18:06:34 2004
@@ -362,7 +362,7 @@
 }
 
 static struct pci_driver mtd_pci_driver = {
-	.name =		"MTD PCI",
+	.name =		"MTD_PCI",
 	.probe =	mtd_pci_probe,
 	.remove =	__devexit_p(mtd_pci_remove),
 	.id_table =	mtd_pci_ids,
===== drivers/mtd/maps/scb2_flash.c 1.4 vs edited =====
--- 1.4/drivers/mtd/maps/scb2_flash.c	Thu Jul 15 10:31:48 2004
+++ edited/drivers/mtd/maps/scb2_flash.c	Mon Aug  9 18:06:53 2004
@@ -229,7 +229,7 @@
 };
 
 static struct pci_driver scb2_flash_driver = {
-	.name =     "Intel SCB2 BIOS Flash",
+	.name =     "Intel_SCB2_BIOS",
 	.id_table = scb2_flash_pci_ids,
 	.probe =    scb2_flash_probe,
 	.remove =   __devexit_p(scb2_flash_remove),

-- 
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  4:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  4:37 Deepak Saxena [this message]
2004-08-10 11:37 ` [PATCH 2.6] Remove spaces from MTD pci_driver.name field Alan Cox

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=20040810043710.GA11719@plexity.net \
    --to=dsaxena@plexity.net \
    --cc=dwmw2@infradead.org \
    --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.