All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: bwindle@fint.org
Cc: ambx1@neo.rr.com, linux-kernel@vger.kernel.org
Subject: Re: [2.5.51] unknown field 'driver_data' compiling cs4243
Date: Tue, 10 Dec 2002 14:55:36 -0800	[thread overview]
Message-ID: <200212102255.OAA00649@baldur.yggdrasil.com> (raw)

Burton Windle writes:
>I'm getting an error compiling cs4232 in 2.5.51. It built fine in 50-bk6.
[...]
>sound/oss/cs4232.c:361: unknown field `driver_data' specified in initializer
[etc.]

	This is not due to the change that I submitted removing
driver_data from struct pci_dev, although it looks like a similar change
for isapnp devices.  I started to make a change to convert
the references to driver_data to
dev_set_drvdata(&isapnpdev->dev,...) and dev_get_drvdata(&isapnpdev->dev),
but got a little confused by the multiple classes of isapnp drivers:

	Driver structure	Device structure	ID structure

include/linux/isapnp.h:
	isapnp_driver		pci_dev			isapnp_device_id
	(none)			pci_bus			isapnp_card_id

include/linux/pnp.h:
	pnpc_driver		pnp_card		pnp_card_id
	pnp_driver		pnp_dev			pnp_id


	From ChangeLog-2.5.51, I see mention of isapnp changes
associated with Adam Belay.  So, I'm cc'ing him as he is probably
much better qualified to explain.

Adam J. Richter     __     ______________   575 Oroville Road
adam@yggdrasil.com     \ /                  Milpitas, California 95035
+1 408 309-6081         | g g d r a s i l   United States of America
                         "Free Software For The Rest Of Us."

             reply	other threads:[~2002-12-10 22:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 22:55 Adam J. Richter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-10 15:02 [2.5.51] unknown field 'driver_data' compiling cs4243 Burton Windle

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=200212102255.OAA00649@baldur.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --cc=ambx1@neo.rr.com \
    --cc=bwindle@fint.org \
    --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.