Re: [2.6 patch] change the SOUND_PRIME handling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Adrian Bunk <[email protected]> wrote:
>
> SOUND_PRIME (for OSS) is a tristate.
> 
>  This doesn't make much sense if most users are checking for 
>  SOUND_PRIME!=0.
> 
>  This patch changes the semantics of SOUND_PRIME to being a limit for all 
>  OSS modules, IOW: SOUND_PRIME=m does now say that all OSS drivers can 
>  only be modular.
> 
>  As a side effect, since SOUND_PRIME already depends on SOUND, there's no 
>  longer a reason for drivers depending on SOUND_PRIME to additionally 
>  depend on SOUND.

This spits lots of rejects because it had dependencies on Sam's trees and
I've dropped all bk trees.  Please fix it up in a week or three.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux