mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: Stefan Agner <stefan@agner.ch>
Cc: Dave Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-kernel@vger.kernel.org, shawnguo@kernel.org,
	meng.yi@nxp.com, Jianwei Wang <jianwei.wang.chn@gmail.com>
Subject: Re: [PATCH] MAINTAINERS: update for Freescale DCU DRM driver
Date: Wed, 27 Jan 2016 17:57:05 -0800	[thread overview]
Message-ID: <b432c6c5af24d6b005ffa1538f42b12c@agner.ch> (raw)
In-Reply-To: <CANk3uyD=OWbOwr2fORXB2n=anCrzc3anHCYnD1sYD2kKFwFHLg@mail.gmail.com>

On 2016-01-07 05:21, Jianwei Wang wrote:
> Acked-by: Jianwei Wang <jianwei.wang.chn@gmail.com>

Applied and pushed to my git tree:
http://git.agner.ch/gitweb/?p=linux-drm-fsl-dcu.git;a=shortlog;h=refs/heads/for-next

Along with this patch, I will queue some DRM DCU patches currently
waiting to be applied. I plan to send a pull request to Dave for the 4.6
merge window.

--
Stefan

> 
> On Thu, Jan 7, 2016 at 2:02 PM, Stefan Agner <stefan@agner.ch> wrote:
>> Promote myself as new maintainer of the Freescale DCU DRM driver.
>>
>> Signed-off-by: Stefan Agner <stefan@agner.ch>
>> ---
>> This has been previously discussed privately. The original driver
>> author and maintainer Jianwei does not work for Freescale anymore
>> and can not carve out spare time to maintain the driver.
>>
>> As I started to make use of the driver on the Freescale Vybrid SoC
>> and already posted several fixes and improvements, I am willing to
>> maintain the driver.
>>
>> Thanks Jianwei for your work on that driver!
>>
>> Dave, I hope you are OK with that?
>>
>> I plan to send a pull request with the patches which have been on the
>> ml lately, specifically the "Fix no fb check bug" and my fixes and
>> enhancements patchset, along with this maintainer change, does that
>> sound reasonable?
>>
>> There is one more pending patchset for this drivers, the TCON and
>> Vybrid support patchset, but this is probably not ready yet. I also
>> plan to post another patchset which enables multiple overlay planes
>> and a cursor plane.
>>
>> --
>> Stefan
>>
>>  MAINTAINERS | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index e9caa4b..3f0aea3 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -3678,7 +3678,7 @@ F:        include/drm/exynos*
>>  F:     include/uapi/drm/exynos*
>>
>>  DRM DRIVERS FOR FREESCALE DCU
>> -M:     Jianwei Wang <jianwei.wang.chn@gmail.com>
>> +M:     Stefan Agner <stefan@agner.ch>
>>  M:     Alison Wang <alison.wang@freescale.com>
>>  L:     dri-devel@lists.freedesktop.org
>>  S:     Supported
>> --
>> 2.6.4
>>

  reply	other threads:[~2016-01-28  1:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07  6:02 Stefan Agner
2016-01-07 13:21 ` Jianwei Wang
2016-01-28  1:57   ` Stefan Agner [this message]
2016-01-08  5:03 ` Dave Airlie

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=b432c6c5af24d6b005ffa1538f42b12c@agner.ch \
    --to=stefan@agner.ch \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jianwei.wang.chn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=meng.yi@nxp.com \
    --cc=shawnguo@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

all inboxes | Powered by JetHome®