From: Takashi Iwai <tiwai@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: CVS does not compile
Date: Wed, 16 Feb 2005 11:36:06 +0100 [thread overview]
Message-ID: <s5hmzu4bxm1.wl@alsa2.suse.de> (raw)
In-Reply-To: <1108510893.3772.9.camel@krustophenia.net>
[-- Attachment #1: Type: text/plain, Size: 453 bytes --]
At Tue, 15 Feb 2005 18:41:33 -0500,
Lee Revell wrote:
>
> 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.
Try the attached patch.
Takashi
[-- Attachment #2: Type: text/plain, Size: 717 bytes --]
Index: alsa-driver/include/adriver.h
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-driver/include/adriver.h,v
retrieving revision 1.98
diff -u -r1.98 adriver.h
--- alsa-driver/include/adriver.h 14 Feb 2005 13:54:47 -0000 1.98
+++ alsa-driver/include/adriver.h 16 Feb 2005 10:35:16 -0000
@@ -712,12 +712,14 @@
#endif
/* pm_message_t type */
-/* #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 11) */
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 11)
+#include <linux/pm.h>
#ifndef PMSG_FREEZE
typedef u32 /*__bitwise*/ pm_message_t;
#define PMSG_FREEZE 3
#define PMSG_SUSPEND 3
#define PMSG_ON 0
#endif
+#endif
#endif /* __SOUND_LOCAL_DRIVER_H */
next prev parent reply other threads:[~2005-02-16 10:36 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
2005-02-16 10:36 ` Takashi Iwai [this message]
-- 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=s5hmzu4bxm1.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rlrevell@joe-job.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