From: Greg KH <greg@kroah.com>
To: Sudhir Kumar <skumar@linux.vnet.ibm.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
sam@ravnborg.org
Subject: Re: [2.6.24-rc6-mm1]Build failure in drivers/net/ehea/ehea_main.c
Date: Thu, 10 Jan 2008 09:34:18 -0800 [thread overview]
Message-ID: <20080110173418.GA14728@kroah.com> (raw)
In-Reply-To: <20080108163305.GB10026@in.ibm.com>
On Tue, Jan 08, 2008 at 10:03:05PM +0530, Sudhir Kumar wrote:
> Hi Andrew,
> Kernel build fails on my machine with error :
>
>
> LD drivers/net/ehea/built-in.o
> CC [M] drivers/net/ehea/ehea_main.o
> drivers/net/ehea/ehea_main.c: In function ???ehea_driver_sysfs_add???:
> drivers/net/ehea/ehea_main.c:2812: error: ???struct device_driver??? has no
> member named ???kobj???
> drivers/net/ehea/ehea_main.c:2815: error: ???struct device_driver??? has no
> member named ???kobj???
> drivers/net/ehea/ehea_main.c:2818: error: ???struct device_driver??? has no
> member named ???kobj???
> drivers/net/ehea/ehea_main.c: In function ???ehea_driver_sysfs_remove???:
> drivers/net/ehea/ehea_main.c:2830: error: ???struct device_driver??? has no
> member named ???kobj???
> make[3]: *** [drivers/net/ehea/ehea_main.o] Error 1
> make[2]: *** [drivers/net/ehea] Error 2
> make[1]: *** [drivers/net] Error 2
> make: *** [drivers] Error 2
>
> The structure device_driver(in device.h) has a member struct driver_private which
> contains the member kobj (according to drivers/base/base.h).
> But in device.h struct driver_private has been declared localy and
> neither defined nor included from base.h.
> So my effort to use driver->driver_private->obj also does not work.
> (I am surprised from where do you access the struct device_driver)
That is because a driver should not be accessing such a field.
And especially not in this manner, why would this driver be creating a
symlink that has already been created by the driver core? This whole
thing can just be removed with no problems. Can you try just removing
the ehea_driver_sysfs_add and ehea_driver_sysfs_remove functions to
verify this as I don't have the hardware present to test it out.
thanks,
greg k-h
next prev parent reply other threads:[~2008-01-10 17:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 16:33 [2.6.24-rc6-mm1]Build failure in drivers/net/ehea/ehea_main.c Sudhir Kumar
2008-01-10 17:34 ` Greg KH [this message]
2008-01-18 9:16 ` Jan-Bernd Themann
2008-01-25 19:10 ` Nathan Lynch
2008-01-28 18:21 ` Greg KH
2008-01-28 18:24 ` Greg KH
2008-01-28 19:22 ` Nathan Lynch
2008-01-28 19:54 ` Greg KH
2008-01-29 10:12 ` Jan-Bernd Themann
2008-01-29 13:23 ` Greg KH
2008-01-29 14:20 ` Christoph Raisch
2008-02-01 14:37 ` Jan-Bernd Themann
2008-02-07 22:17 ` Greg KH
2008-02-12 15:28 ` Christoph Raisch
2008-01-28 18:25 ` 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=20080110173418.GA14728@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=skumar@linux.vnet.ibm.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