mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Laurent riffard <laurent.riffard@free.fr>
To: linux-kernel@vger.kernel.org, Al Viro <viro@ftp.linux.org.uk>,
	Greg KH <greg@kroah.com>,
	Russell King <rmk+lkml@arm.linux.org.uk>
Subject: [RFC patch 3/3] remove pci_driver.owner and .name fields
Date: Wed, 26 Oct 2005 22:48:05 +0200	[thread overview]
Message-ID: <20051026204909.995658000@antares.localdomain> (raw)
In-Reply-To: <20051026204802.123045000@antares.localdomain>

[-- Attachment #1: remove_pci_driver_owner_name-final_cleanup.patch --]
[-- Type: text/plain, Size: 1659 bytes --]

This is the final cleanup : deletion of pci_driver.name and .owner
happens now. 

Signed-off-by: Laurent Riffard <laurent.riffard@free.fr>
--

 drivers/pci/pci-driver.c |    5 -----
 include/linux/pci.h      |    8 --------
 2 files changed, 13 deletions(-)

Index: linux-2.6-stable/drivers/pci/pci-driver.c
===================================================================
--- linux-2.6-stable.orig/drivers/pci/pci-driver.c
+++ linux-2.6-stable/drivers/pci/pci-driver.c
@@ -339,11 +339,6 @@
 	int error;
 
 	/* initialize common driver fields */
-	if (drv->name) {
-		/* backward compatibility until all pci_driver are converted to
-		 * use pci_driver.driver.name instead of pci_driver.name */
-		drv->driver.name = drv->name;
-	}
 	drv->driver.bus = &pci_bus_type;
 	drv->driver.probe = pci_device_probe;
 	drv->driver.remove = pci_device_remove;
Index: linux-2.6-stable/include/linux/pci.h
===================================================================
--- linux-2.6-stable.orig/include/linux/pci.h
+++ linux-2.6-stable/include/linux/pci.h
@@ -664,14 +664,6 @@
 struct module;
 struct pci_driver {
 	struct list_head node;
-	/*
-	 * Please do not use the 2 following fields, they are planned for
-	 * deletion.
-	 * Use driver.name instead of .name.
-	 * The field driver.owner will be set by pci_register_driver.
-	 */
-	char *name;
-	struct module *owner;
 	const struct pci_device_id *id_table;	/* must be non-NULL for probe to be called */
 	int  (*probe)  (struct pci_dev *dev, const struct pci_device_id *id);	/* New device inserted */
 	void (*remove) (struct pci_dev *dev);	/* Device removed (NULL if not a hot-plug capable driver) */

--


  parent reply	other threads:[~2005-10-26 20:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-26 20:48 [RFC patch 0/3] " Laurent riffard
2005-10-26 20:48 ` [RFC patch 1/3] " Laurent riffard
2005-10-26 21:20   ` Al Viro
2005-10-26 22:53     ` Laurent Riffard
2005-10-26 20:48 ` [RFC patch 2/3] " Laurent riffard
2005-10-26 21:05   ` Roland Dreier
2005-10-26 21:21     ` Al Viro
2005-10-26 21:30       ` Roland Dreier
2005-10-26 21:35       ` Andrew Morton
2005-10-26 20:48 ` Laurent riffard [this message]
2005-10-26 21:11   ` [RFC patch 3/3] " Greg KH
2005-10-26 22:22     ` Laurent Riffard
2005-10-26 22:26       ` Greg KH
2005-10-26 22:57         ` Laurent Riffard
2005-10-26 21:17 ` [RFC patch 0/3] " Al Viro

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=20051026204909.995658000@antares.localdomain \
    --to=laurent.riffard@free.fr \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=viro@ftp.linux.org.uk \
    /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

all inboxes | Powered by JetHome®