mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: John Weber <weber@nyc.rr.com>
Cc: linux-kernel@vger.kernel.org, viro@math.psu.edu
Subject: Re: PCI Hotplug and Linux 2.5.4-pre2
Date: Thu, 7 Feb 2002 10:23:38 -0800	[thread overview]
Message-ID: <20020207182338.GB18310@kroah.com> (raw)
In-Reply-To: <3C62C4AB.3040109@nyc.rr.com>
In-Reply-To: <3C62C4AB.3040109@nyc.rr.com>

On Thu, Feb 07, 2002 at 01:17:15PM -0500, John Weber wrote:
> I can't find the definition of pcihpfs_fs_type used in 
> pci_hotplug_core.c in register_filesystem(), unregister_filesystem(),
> and kern_mount().  This is causing a compilation error.

Here's the fix, I'll send it on.

thanks,

greg k-h


diff -Nru a/drivers/hotplug/pci_hotplug_core.c b/drivers/hotplug/pci_hotplug_core.c
--- a/drivers/hotplug/pci_hotplug_core.c	Thu Feb  7 10:22:25 2002
+++ b/drivers/hotplug/pci_hotplug_core.c	Thu Feb  7 10:22:25 2002
@@ -414,7 +414,7 @@
 	}
 
 	spin_unlock (&mount_lock);
-	mnt = kern_mount (&pcihpfs_fs_type);
+	mnt = kern_mount (&pcihpfs_type);
 	if (IS_ERR(mnt)) {
 		err ("could not mount the fs...erroring out!\n");
 		return -ENODEV;
@@ -1139,7 +1139,7 @@
 	spin_lock_init(&list_lock);
 
 	dbg("registering filesystem.\n");
-	result = register_filesystem(&pcihpfs_fs_type);
+	result = register_filesystem(&pcihpfs_type);
 	if (result) {
 		err("register_filesystem failed with %d\n", result);
 		goto exit;
@@ -1153,7 +1153,7 @@
 
 static void __exit pci_hotplug_exit (void)
 {
-	unregister_filesystem(&pcihpfs_fs_type);
+	unregister_filesystem(&pcihpfs_type);
 }
 
 module_init(pci_hotplug_init);

  reply	other threads:[~2002-02-07 18:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-07 18:17 John Weber
2002-02-07 18:23 ` Greg KH [this message]
2002-02-07 18:32 ` Brian Strand
2002-02-07 18:50   ` Dave Jones

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=20020207182338.GB18310@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    --cc=weber@nyc.rr.com \
    /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®