Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Matthias Saou <matthias@rpmforge.net>
Cc: alsa-devel@lists.sourceforge.net, jsanders@teklinks.com,
	jason@corekin.no-ip.com
Subject: Re: Re: [Alsa-user] alsa cvs, redhat9, kernel 2-4-20-8
Date: Mon, 07 Apr 2003 17:44:40 +0200	[thread overview]
Message-ID: <s5hu1daqplj.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030407122753.104effb3.matthias@rpmforge.net>

At Mon, 7 Apr 2003 12:27:53 +0200,
Matthias Saou wrote:
> 
> Takashi Iwai <tiwai@suse.de> wrote :
> 
> > the current alsa code checks the existence of __WORK_INITIALIZER
> > macro.  if it's defined, no wrapper function is used.
> > in rh's include/linux/workqueue.h, is this macro defined?
> 
> Yes, it is... from /usr/src/linux-2.4.20-x/include/linux/workqueue.h:
> 
> #define __WORK_INITIALIZER(n, f, d) {                           \
>         .entry  = { &(n).entry, &(n).entry },                   \
>         .func = (f),                                            \
>         .data = (d) }

hmm, then it should be ok.  the configure and make should work without
any patches.

did anyone build successfully with RH9 and RH's kernel?


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/

  reply	other threads:[~2003-04-07 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <se8e13a5.075@mail.teklinks.com>
     [not found] ` <20030405120028.6812ba7e.matthias@rpmforge.net>
2003-04-07 10:19   ` [Alsa-user] alsa cvs, redhat9, kernel 2-4-20-8 Takashi Iwai
2003-04-07 10:27     ` Matthias Saou
2003-04-07 15:44       ` Takashi Iwai [this message]
2003-04-09  4:58     ` Lance A. Brown

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=s5hu1daqplj.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=jason@corekin.no-ip.com \
    --cc=jsanders@teklinks.com \
    --cc=matthias@rpmforge.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