From: Jingoo Han <jg1.han@samsung.com>
To: 'Tomi Valkeinen' <tomi.valkeinen@ti.com>,
'Jean-Christophe PLAGNIOL-VILLARD' <plagnioj@jcrosoft.com>
Cc: 'Florian Tobias Schandinat' <FlorianSchandinat@gmx.de>,
'Arnd Bergmann' <arnd@arndb.de>,
'Olof Johansson' <olof@lixom.net>,
linux-fbdev@vger.kernel.org,
'Linus Torvalds' <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
'Andrew Morton'
<akpm@linux-foundation.org>linux-kernel@vger.kernel.org,
Jingoo Han <jg1.han@samsung.com>
Subject: Re: [RFC] Add co-maintainer for fbdev
Date: Mon, 27 May 2013 08:19:10 +0000 [thread overview]
Message-ID: <001501ce5ab2$dd2e9860$978bc920$@samsung.com> (raw)
In-Reply-To: <51A31013.9010701@ti.com>
On Monday, May 27, 2013 4:50 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>
> Hi Jean-Christophe,
>
> >>> On Fri, May 24, 2013 at 8:38 AM, Jean-Christophe PLAGNIOL-VILLARD
> >>> <plagnioj@jcrosoft.com> wrote:
> >>>> Hi Florian,
> >>>>
> >>>> As you seems very busy I'd like to propose the help you to handle the
> >>>> fbdev subsystem to easier the rich of the fbdev patch to Linus
> >>>>
> >>>> As I'm working on fbdev on at91 and others and already Co-Maintain the
> >>>> at91 mach on ARM
> >>>>
> >>>> And if you are not willing to continue I could take over
>
> I've been collecting fbdev patches for the latest merge windows, so that
> Linus doesn't get tons of small separate pull requests. But I haven't
> been very proactive with that, and I don't think I have time to really
> maintain fbdev.
Hi Tomi,
I really thank you for your previous efforts.
Actually, I thought that you're a good fit for fbdev.
>
> So I'd also welcome somebody stepping up and taking taking on the
> maintainership of fbdev.
Hi Jean-Christophe PLAGNIOL-VILLARD,
I agree with Tomi's opinion.
If you take the maintainership of fbdev, it will be very helpful.
Best regards,
Jingoo Han
>
> Tomi
>
> Ps. I already have a few patches for 3.10 and for 3.11. I'll send them
> to you.
>
WARNING: multiple messages have this Message-ID (diff)
From: Jingoo Han <jg1.han@samsung.com>
To: "'Tomi Valkeinen'" <tomi.valkeinen@ti.com>,
"'Jean-Christophe PLAGNIOL-VILLARD'" <plagnioj@jcrosoft.com>
Cc: "'Florian Tobias Schandinat'" <FlorianSchandinat@gmx.de>,
"'Arnd Bergmann'" <arnd@arndb.de>,
"'Olof Johansson'" <olof@lixom.net>,
linux-fbdev@vger.kernel.org,
"'Linus Torvalds'" <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"'Andrew Morton'" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Jingoo Han <jg1.han@samsung.com>
Subject: Re: [RFC] Add co-maintainer for fbdev
Date: Mon, 27 May 2013 17:19:10 +0900 [thread overview]
Message-ID: <001501ce5ab2$dd2e9860$978bc920$@samsung.com> (raw)
In-Reply-To: <51A31013.9010701@ti.com>
On Monday, May 27, 2013 4:50 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>
> Hi Jean-Christophe,
>
> >>> On Fri, May 24, 2013 at 8:38 AM, Jean-Christophe PLAGNIOL-VILLARD
> >>> <plagnioj@jcrosoft.com> wrote:
> >>>> Hi Florian,
> >>>>
> >>>> As you seems very busy I'd like to propose the help you to handle the
> >>>> fbdev subsystem to easier the rich of the fbdev patch to Linus
> >>>>
> >>>> As I'm working on fbdev on at91 and others and already Co-Maintain the
> >>>> at91 mach on ARM
> >>>>
> >>>> And if you are not willing to continue I could take over
>
> I've been collecting fbdev patches for the latest merge windows, so that
> Linus doesn't get tons of small separate pull requests. But I haven't
> been very proactive with that, and I don't think I have time to really
> maintain fbdev.
Hi Tomi,
I really thank you for your previous efforts.
Actually, I thought that you're a good fit for fbdev.
>
> So I'd also welcome somebody stepping up and taking taking on the
> maintainership of fbdev.
Hi Jean-Christophe PLAGNIOL-VILLARD,
I agree with Tomi's opinion.
If you take the maintainership of fbdev, it will be very helpful.
Best regards,
Jingoo Han
>
> Tomi
>
> Ps. I already have a few patches for 3.10 and for 3.11. I'll send them
> to you.
>
next prev parent reply other threads:[~2013-05-27 8:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 15:38 [RFC] Add co-maintainer for fbdev Jean-Christophe PLAGNIOL-VILLARD
2013-05-24 15:38 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-24 17:30 ` Olof Johansson
2013-05-24 17:30 ` Olof Johansson
2013-05-24 18:56 ` Arnd Bergmann
2013-05-24 18:56 ` Arnd Bergmann
2013-05-26 23:41 ` Florian Tobias Schandinat
2013-05-27 7:49 ` Tomi Valkeinen
2013-05-27 7:49 ` Tomi Valkeinen
2013-05-27 8:19 ` Jingoo Han [this message]
2013-05-27 8:19 ` Jingoo Han
2013-05-27 12:42 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-27 12:42 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-27 14:38 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-27 14:38 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-28 21:19 ` Arnd Bergmann
2013-05-28 21:19 ` Arnd Bergmann
2013-05-29 0:34 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-29 0:34 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-29 1:32 ` Jingoo Han
2013-05-29 1:32 ` Jingoo Han
2013-05-29 20:53 ` Andrew Morton
2013-05-29 20:53 ` Andrew Morton
2013-05-30 7:21 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-30 7:21 ` Jean-Christophe PLAGNIOL-VILLARD
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='001501ce5ab2$dd2e9860$978bc920$@samsung.com' \
--to=jg1.han@samsung.com \
--cc=FlorianSchandinat@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.