From: joeyli <jlee@suse.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpu: schedule gma500 stub driver for feature removal
Date: Wed, 23 May 2012 09:48:48 +0800 [thread overview]
Message-ID: <1337737728.9751.236.camel@linux-s257.site> (raw)
In-Reply-To: <CADnq5_M7sSMhMM8ASJ-VOCdZBEx3yo3+P29WgwHRZ-Ls3zHoEA@mail.gmail.com>
Hi Alex,
於 二,2012-05-22 於 12:01 -0400,Alex Deucher 提到:
> On Mon, May 21, 2012 at 11:15 AM, Lee, Chun-Yi <joeyli.kernel@gmail.com> 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.
>
>
> December 2013?
>
> Alex
My plan is December 2012, end of this year.
Thanks
Joey Lee
> >
> > Signed-off-by: Lee, Chun-Yi <jlee@suse.com>
> > ---
> > Documentation/feature-removal-schedule.txt | 11 +++++++++++
> > 1 files changed, 11 insertions(+), 0 deletions(-)
> >
> > diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
> > index a0ffac0..219d6f1 100644
> > --- a/Documentation/feature-removal-schedule.txt
> > +++ b/Documentation/feature-removal-schedule.txt
> > @@ -524,3 +524,14 @@ Files: arch/arm/mach-at91/at91cap9.c
> > Why: The code is not actively maintained and platforms are now hard to find.
> > Who: Nicolas Ferre <nicolas.ferre@atmel.com>
> > Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> > +
> > +----------------------------
> > +
> > +What: Intel GMA500 Stub Driver
> > +When: December 2012
> > +Why: 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.
> > +Who: Lee, Chun-Yi <jlee@novell.com>
> > --
> > 1.6.0.2
> >
> > _______________________________________________
> > dri-devel mailing list
> > dri-devel@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/dri-devel
>
next prev parent reply other threads:[~2012-05-23 1:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 15:15 Lee, Chun-Yi
2012-05-22 16:01 ` Alex Deucher
2012-05-23 1:48 ` joeyli [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=1337737728.9751.236.camel@linux-s257.site \
--to=jlee@suse.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/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