From: Greg KH <greg@kroah.com>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test3 current - firewire compile error
Date: Sat, 16 Aug 2003 09:35:53 -0700 [thread overview]
Message-ID: <20030816163553.GA9735@kroah.com> (raw)
In-Reply-To: <3F3E288B.3010105@cornell.edu>
On Sat, Aug 16, 2003 at 08:50:19AM -0400, Ivan Gyurdiev wrote:
> Hopefully, this is not a duplicate post:
> ===========================================
>
> drivers/ieee1394/nodemgr.c: In function `nodemgr_update_ud_names':
> drivers/ieee1394/nodemgr.c:471: error: structure has no member named `name'
> drivers/ieee1394/nodemgr.c: In function `nodemgr_create_node':
> drivers/ieee1394/nodemgr.c:723: error: structure has no member named `name'
> drivers/ieee1394/nodemgr.c: In function `nodemgr_update_node':
> drivers/ieee1394/nodemgr.c:1318: error: structure has no member named `name'
> drivers/ieee1394/nodemgr.c: In function `nodemgr_add_host':
> drivers/ieee1394/nodemgr.c:1775: error: structure has no member named `name'
> make[2]: *** [drivers/ieee1394/nodemgr.o] Error 1
> make[1]: *** [drivers/ieee1394] Error 2
> make: *** [drivers] Error 2
I removed struct device.name and forgot to change the firewire code :(
I'll work on a patch for this later this evening, unless someone beats
me to it.
Sorry,
greg k-h
next prev parent reply other threads:[~2003-08-16 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 12:50 2.6.0-test3 current - firewire compile error Ivan Gyurdiev
2003-08-16 7:11 ` walt
2003-08-16 13:59 ` 2.6.0-test3 current - compile error - no member named 'name' Ivan Gyurdiev
2003-08-16 16:37 ` Greg KH
2003-08-16 16:36 ` 2.6.0-test3 current - firewire compile error Greg KH
2003-08-16 17:22 ` Adam Belay
2003-08-16 22:16 ` walt
2003-08-16 16:35 ` Greg KH [this message]
2003-08-16 17:38 ` OGAWA Hirofumi
2003-08-16 19:16 ` Greg KH
2003-08-16 19:15 ` 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=20030816163553.GA9735@kroah.com \
--to=greg@kroah.com \
--cc=ivg2@cornell.edu \
--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.