From: Stevie Trujillo <stevie.trujillo@gmail.com>
To: marco.stornelli@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: ramoops: is using platform_drivers correct?
Date: Mon, 23 May 2011 15:27:53 +0200 [thread overview]
Message-ID: <201105231527.53805.stevie.trujillo@gmail.com> (raw)
Hello,
ramoops (drivers/char/ramoops.c) is for "all" computers right? When I try to
load it on my laptop, I get ENODEV. This is caused by platform_driver_probe()
- the code never reaches the ramoops probe callback.
After I removed the platform_driver stuff, moving everything into ramoops_init
and ramoops_exit it worked.
next reply other threads:[~2011-05-23 13:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 13:27 Stevie Trujillo [this message]
2011-05-23 14:10 ` ramoops: is using platform_drivers correct? Américo Wang
2011-05-23 14:36 ` Kyungmin Park
2011-05-24 5:32 ` Kyungmin Park
2011-05-24 5:49 ` Américo Wang
2011-05-24 6:14 ` Kyungmin Park
2011-05-24 14:12 ` Américo Wang
2011-05-24 14:16 ` Kyungmin Park
2011-05-24 14:28 ` Stevie Trujillo
2011-05-24 17:03 ` Marco Stornelli
2011-05-25 13:24 ` Américo Wang
2011-05-25 14:07 ` Marco Stornelli
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=201105231527.53805.stevie.trujillo@gmail.com \
--to=stevie.trujillo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.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