From: alexey.kodanev@oracle.com
To: linux-acpi@vger.kernel.org
Cc: ltp-list@lists.sourceforge.net,
Vasily Isaenko <vasily.isaenko@oracle.com>
Subject: ACPI test
Date: Fri, 13 Sep 2013 16:20:51 +0400 [thread overview]
Message-ID: <52330323.6020702@oracle.com> (raw)
Hi All!
I'm reviewing Linux Test Project's test concerning ACPI and a little bit
lost with the following test:
https://github.com/linux-test-project/ltp/tree/master/testcases/kernel/device-drivers/acpi.
It's quite outdated...
Pardon my technical knowledge on this subject but could you guide me to
solve the following questions about the test and ACPI:
* Is it necessary to use block device to test ACPI functionality as test
does?
* How can I verify data which I get from acpi_driver_data() using random
acpi device handle? The test is using its own 'acpi_ec' structure and
trying to cast return void pointer from that function to it, but in the
kernel, this structure is slightly different and defined internally.
May be you have some thoughts how ACPI test should look like? Any help
is appreciated.
Many thanks,
Alexey
reply other threads:[~2013-09-13 12:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52330323.6020702@oracle.com \
--to=alexey.kodanev@oracle.com \
--cc=linux-acpi@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=vasily.isaenko@oracle.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;
as well as URLs for NNTP newsgroup(s).