From: Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: Changes to of_device ?
Date: Fri, 17 Jun 2011 15:53:06 +0200 [thread overview]
Message-ID: <201106171553.06443.dargaud@lpsc.in2p3.fr> (raw)
In-Reply-To: <4DFB516C.4060602@gate-nine.de>
> I'm sorry, I should have mentioned that struct of_device was replaced by
> struct platform_device. So in order to get your code compiled, you have
> to change the probe function to
>
> static int xad_driver_probe(struct platform_device* dev, const struct
> of_device_id *match) {
Thanks, that worked...
Side question: how do you guy find your way inside the kernel ? I spent hours trying to find the declarations of various
basic structs like device, of_node, etc even with ack-grep and ctags (which I probably don't know how to use very well).
--
Guillaume Dargaud
http://www.gdargaud.net/
next prev parent reply other threads:[~2011-06-17 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 9:19 Changes to of_device ? Guillaume Dargaud
2011-06-17 10:55 ` Philipp Ittershagen
2011-06-17 11:22 ` Guillaume Dargaud
2011-06-17 12:57 ` Philipp Ittershagen
2011-06-17 13:06 ` Philipp Ittershagen
2011-06-17 13:53 ` Guillaume Dargaud [this message]
2011-06-17 14:08 ` Grant Likely
2011-06-17 14:23 ` David Laight
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=201106171553.06443.dargaud@lpsc.in2p3.fr \
--to=dargaud@lpsc.in2p3.fr \
--cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox