From: Dave Jones <davej@codemonkey.org.uk>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: acpi spinlock breakage
Date: Wed, 2 Apr 2003 17:21:26 +0100 [thread overview]
Message-ID: <20030402162119.GA19179@suse.de> (raw)
osl stuff looks really borked in current 2.5-bk ..
drivers/acpi/osl.c: In function `acpi_os_acquire_lock':
drivers/acpi/osl.c:739: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:739: request for member `magic' in something not a structure or union
drivers/acpi/osl.c:739: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:739: request for member `lock' in something not a structure or union
drivers/acpi/osl.c:739: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:739: request for member `babble' in something not a structure or union
drivers/acpi/osl.c:739: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:739: request for member `module' in something not a structure or union
drivers/acpi/osl.c:739: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:739: request for member `owner' in something not a structure or union
drivers/acpi/osl.c:739: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:739: request for member `oline' in something not a structure or union
drivers/acpi/osl.c:739: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:739: request for member `babble' in something not a structure or union
drivers/acpi/osl.c:739: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:739: request for member `lock' in something not a structure or union
drivers/acpi/osl.c:739: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:739: request for member `owner' in something not a structure or union
drivers/acpi/osl.c:739: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:739: request for member `oline' in something not a structure or union
drivers/acpi/osl.c: In function `acpi_os_release_lock':
drivers/acpi/osl.c:758: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:758: request for member `magic' in something not a structure or union
drivers/acpi/osl.c:758: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:758: request for member `lock' in something not a structure or union
drivers/acpi/osl.c:758: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:758: request for member `babble' in something not a structure or union
drivers/acpi/osl.c:758: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:758: request for member `module' in something not a structure or union
drivers/acpi/osl.c:758: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:758: request for member `babble' in something not a structure or union
drivers/acpi/osl.c:758: warning: dereferencing `void *' pointer
drivers/acpi/osl.c:758: request for member `lock' in something not a structure or union
make[2]: *** [drivers/acpi/osl.o] Error 1
make[1]: *** [drivers/acpi] Error 2
make: *** [drivers] Error 2
Looks like its trying to spin_lock an 'acpi_handle',
which is typedef'd to void *
Dave
next reply other threads:[~2003-04-02 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 16:21 Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-03 17:26 acpi spinlock breakage Shawn Starr
2003-04-03 17:45 ` Dave Jones
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=20030402162119.GA19179@suse.de \
--to=davej@codemonkey.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox