public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Peter Waechtler <pwaechtler@mac.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [2.5 patch] fix sound/oss/ics2101.c compilation
Date: Mon, 31 Mar 2003 12:05:03 +0200	[thread overview]
Message-ID: <20030331100503.GD22827@fs.tum.de> (raw)
In-Reply-To: <1049068012.2798.13.camel@picklock>

On Mon, Mar 31, 2003 at 02:04:04AM +0200, Peter Waechtler wrote:
> 
> There's a problem when compiling the GUS driver into the kernel
> instead of as a module. I renamed the global "lock" to "gus_lock"
> and made sure that it's used (shared by gus_midi, gus_wave, ics2101)
> 
> [snippet of sound/oss/Makefile]
> obj-$(CONFIG_SOUND_GUS)         += gus.o ad1848.o
> gus-objs        := gus_card.o gus_midi.o gus_vol.o gus_wave.o ics2101.o
> 
> 
> Adrian: Do you have a GUS and can test this?

Unfortunately not, I noticed this problem while doing compile-only tests 
with a .config that has as much as possible enabled.

BTW:
The sound/oss/mad16.c part of your patch doesn't belong to this problem?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2003-03-31  9:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 20:10 [2.5 patch] fix sound/oss/ics2101.c compilation Adrian Bunk
2003-03-23 18:11 ` Peter Waechtler
2003-03-30  9:30   ` Adrian Bunk
2003-03-31  0:04     ` Peter Waechtler
2003-03-31 10:05       ` Adrian Bunk [this message]
2003-03-31 12:14         ` [2.5 patch] typo fix for compilation Peter Waechtler

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=20030331100503.GD22827@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pwaechtler@mac.com \
    --cc=torvalds@transmeta.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