From: Nathan Lynch <ntl@pobox.com>
To: Greg KH <greg@kroah.com>
Cc: Jan-Bernd Themann <ossthema@de.ibm.com>,
Sudhir Kumar <skumar@linux.vnet.ibm.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
sam@ravnborg.org, Christoph Raisch <raisch@de.ibm.com>
Subject: Re: [2.6.24-rc6-mm1]Build failure in drivers/net/ehea/ehea_main.c
Date: Mon, 28 Jan 2008 13:22:04 -0600 [thread overview]
Message-ID: <20080128192204.GO14201@localdomain> (raw)
In-Reply-To: <20080128182423.GC28861@kroah.com>
Greg KH wrote:
> On Fri, Jan 25, 2008 at 01:10:48PM -0600, Nathan Lynch wrote:
> > Jan-Bernd Themann wrote:
> > >
> > > On Thursday 10 January 2008 18:34, Greg KH wrote:
> > > > > 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.
> > >
> > > The eHEA driver tries to orginize its sys-entries as close as possible to
> > > other ethernet drivers. Each eHEA NIC has multiple ports which is not that
> > > common in PCI. This means that each port is represented by a subdirectory
> > > which has not the "driver" sys-link, only the root directory has.
> > > Some tools expect to have this driver link in each port directory.
> > > That is the reason why this link is created manually.
> > >
> > > Are there any other ways to create this link?
> >
> >
> > This is now broken in mainline...
> >
> > 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'
>
> Does the patch below fix this? That driver should not have been trying
> to create symlinks that the driver core has already created for it.
Yes, it fixes the build error, by just removing the code that got
broken. Jan-Bernd gave a rationale for creating the symlink that
didn't really seem to be answered.
next prev parent reply other threads:[~2008-01-28 19:22 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
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 [this message]
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=20080128192204.GO14201@localdomain \
--to=ntl@pobox.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ossthema@de.ibm.com \
--cc=raisch@de.ibm.com \
--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