From: Greg KH <greg@kroah.com>
To: Benjamin Pharr <ben@benpharr.com>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: inode.c Compile Error
Date: Thu, 7 Feb 2002 08:05:25 -0800 [thread overview]
Message-ID: <20020207160524.GO14504@kroah.com> (raw)
In-Reply-To: <20020207151518.GA5184@hst000004380um.kincannon.olemiss.edu>
In-Reply-To: <20020207151518.GA5184@hst000004380um.kincannon.olemiss.edu>
On Thu, Feb 07, 2002 at 09:15:18AM -0600, Benjamin Pharr wrote:
> I got the following error when trying to compile 2.5.4-pre2:
This patch fixes this. I'll send it upstream later today.
thanks,
greg k-h
diff -Nru a/drivers/usb/inode.c b/drivers/usb/inode.c
--- a/drivers/usb/inode.c Thu Feb 7 08:08:34 2002
+++ b/drivers/usb/inode.c Thu Feb 7 08:08:34 2002
@@ -525,7 +525,7 @@
static struct super_block *usb_get_sb(struct file_system_type *fs_type,
int flags, char *dev_name, void *data)
{
- return get_sb_single(fs_type, flags, data, usb_fill_super);
+ return get_sb_single(fs_type, flags, data, usbfs_fill_super);
}
static struct file_system_type usbdevice_fs_type = {
prev parent reply other threads:[~2002-02-07 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 15:15 inode.c Compile Error Benjamin Pharr
2002-02-07 16:05 ` Greg KH [this message]
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=20020207160524.GO14504@kroah.com \
--to=greg@kroah.com \
--cc=ben@benpharr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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