From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Lee, Chun-Yi" <jlee@suse.com>,
randy.dunlap@oracle.com, mjg59@srcf.ucam.org, gregkh@suse.de,
trenn@suse.de, Valdis.Kletnieks@vt.edu, Dennis.Jansen@web.de,
airlied@redhat.com, eric@anholt.net, alexdeucher@gmail.com,
bskeggs@redhat.com, chris@chris-wilson.co.uk
Subject: Re: [PATCH] gpu: schedule gma500 stub driver for feature removal
Date: Fri, 25 May 2012 15:13:54 +0100 [thread overview]
Message-ID: <20120525151354.4912e458@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <20120524195350.GA11545@kroah.com>
On Fri, 25 May 2012 04:53:50 +0900
Greg KH <gregkh@linuxfoundation.org> wrote:
> On Mon, May 21, 2012 at 11:23:36PM +0800, Lee, Chun-Yi wrote:
> > In v3.3, the gma500 drm driver moved from staging to drm group by
> > Alan Cox's 3abcf41fb patch. the gma500 drm driver should control
> > brightness well and don't need gma500 stub driver anymore.
> >
> > So, my plan is remove gma500 stub driver at Dec. 2012.
>
> Why not just remove it right now as it's not needed at all anymore?
If there are distros not currently ahipping the GMA500 driver or people
updating old kernels using vesa and not having the right server bits it
might cause them problems - giving it 6 months isn't a bad idea IMHO
next prev parent reply other threads:[~2012-05-25 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 15:23 Lee, Chun-Yi
2012-05-24 19:53 ` Greg KH
2012-05-24 23:19 ` joeyli
2012-05-25 14:13 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-21 15:15 Lee, Chun-Yi
2012-05-22 16:01 ` Alex Deucher
2012-05-23 1:48 ` joeyli
2012-03-20 2:47 Lee, Chun-Yi
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=20120525151354.4912e458@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Dennis.Jansen@web.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=airlied@redhat.com \
--cc=alexdeucher@gmail.com \
--cc=bskeggs@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=gregkh@suse.de \
--cc=jlee@suse.com \
--cc=joeyli.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=randy.dunlap@oracle.com \
--cc=trenn@suse.de \
/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
Powered by JetHome