mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Dave Airlie <airlied@linux.ie>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	lkml <linux-kernel@vger.kernel.org>,
	akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH -next] drm: sis depends on FB_SIS
Date: Tue, 12 Aug 2008 15:59:06 +0300	[thread overview]
Message-ID: <20080812125906.GC13910@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <alpine.DEB.0.82.0808080309270.13875@skynet.skynet.ie>

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


  reply	other threads:[~2008-08-12 13:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07 15:32 Randy Dunlap
2008-08-07 23:09 ` Dave Airlie
2008-08-08  0:55   ` Randy Dunlap
2008-08-08  2:11     ` Dave Airlie
2008-08-12 12:59       ` Adrian Bunk [this message]
2008-08-12 21:37         ` Dave Airlie
2008-08-13 21:57           ` [RFC: -next patch] don't allow FB_SIS=m, DRM_SIS=y Adrian Bunk
2008-08-19 22:31             ` Randy Dunlap

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=20080812125906.GC13910@cs181140183.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.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

all inboxes | Powered by JetHome®