linux-kernel - Re: [PATCH -next] drm: sis depends on FB

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 Aug 2008 15:59:06 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Dave Airlie <airlied@...ux.ie>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	lkml <linux-kernel@...r.kernel.org>,
	akpm <akpm@...ux-foundation.org>
Subject: Re: [PATCH -next] drm: sis depends on FB_SIS

On Fri, Aug 08, 2008 at 03:11:03AM +0100, Dave Airlie wrote:
> 
> > > If someone asks for sisfb then sis drm uses code from it, if they don't 
> > > ask for it it doesn't. So I want sisfb to be built in if its selected and 
> > > sis drm is built-in.
> > 
> > config DRM_SIS
> > 	select FB_SIS
> 
> Maybe the other way around, I don't want DRM_SIS influencing whether 
> FB_SIS is on or off, if the user wants sisfb on, then when they select it, 
> DRM_SIS should be built in the same way. But if sisfb isn't selected by 
> the user, then selecting DRM_SIS shouldn't enable it.

If FB_SIS=m, should DRM_SIS=y be allowed or should in this case DRM_SIS 
be restricted to n/m?

> Dave.

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

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