From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: CVS does not compile
Date: Tue, 15 Feb 2005 18:41:33 -0500 [thread overview]
Message-ID: <1108510893.3772.9.camel@krustophenia.net> (raw)
In-Reply-To: <1108501339.3772.5.camel@krustophenia.net>
On Tue, 2005-02-15 at 16:02 -0500, Lee Revell wrote:
> from /smb/rlrevell/cvs/alsa-default-2/alsa-driver/acore/hwdep.c:28:
> include/linux/pm.h:198: error: redefinition of `pm_message_t'
> /smb/rlrevell/cvs/alsa-default-2/alsa-driver/include/adriver.h:717:
> error: `pm_message_t' previously declared here
If I back out this patch it works fine.
Lee
Index: include/adriver.h
===================================================================
RCS file: /cvsroot/alsa/alsa-driver/include/adriver.h,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -u -r1.105 -r1.106
--- include/adriver.h 7 Feb 2005 08:29:13 -0000 1.105
+++ include/adriver.h 14 Feb 2005 13:55:43 -0000 1.106
@@ -712,7 +712,8 @@
#endif
/* pm_message_t type */
-#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 11)
+/* #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 11) */
+#ifndef PMSG_FREEZE
typedef u32 /*__bitwise*/ pm_message_t;
#define PMSG_FREEZE 3
#define PMSG_SUSPEND 3
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-15 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 21:02 CVS does not compile Lee Revell
2005-02-15 23:41 ` Lee Revell [this message]
2005-02-16 10:36 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2004-11-03 20:03 Lee Revell
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=1108510893.3772.9.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
/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