From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-fbdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] fbdev: remove current maintainer
Date: Tue, 20 Dec 2016 15:16:51 +0200 [thread overview]
Message-ID: <224e34da-d694-121a-693d-417fe81b19ee@ti.com> (raw)
In-Reply-To: <7413786.2DSvSX0P97@amdc3058>
[-- Attachment #1.1: Type: text/plain, Size: 1079 bytes --]
On 19/12/16 15:34, Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> On Thursday, December 15, 2016 12:12:52 PM Andrew Morton wrote:
>> On Thu, 8 Dec 2016 10:34:12 +0200 Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
>>
>>> Remove Tomi Valkeinen from fbdev maintainer and mark fbdev as orphan.
>>>
>>> ...
>>>
>>> I just don't have time to even pretend I maintain fbdev, so mark it as Orphan.
>>>
>>> Anyone want to pick fbdev maintainership?
>
> http://marc.info/?l=linux-fbdev&m=148181317415549&w=2
>
>> I'll keep an eye on the mailing list, try to ensure that things keep
>> ticking along.
>
> Andrew, do you want to manage patches yourself or should I step
> in and try to do it?
>
> Tomi, in case I would end up handling patches your help would be
> still greatly appreciated (I'm not much a fbdev expert so any
> non-obvious stuff will likely take some time to be processed)..
Yes, I can have a look (but no promises). But I'm no fbdev expert either
=). I think I was mostly acting as a gate-keeper to sort the worst
problems out.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-12-20 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 8:34 Tomi Valkeinen
2016-12-08 10:04 ` Daniel Vetter
2016-12-20 1:17 ` Laurent Pinchart
2016-12-15 20:12 ` Andrew Morton
2016-12-19 13:34 ` Bartlomiej Zolnierkiewicz
2016-12-19 18:13 ` Andrew Morton
2016-12-20 13:16 ` Tomi Valkeinen [this message]
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=224e34da-d694-121a-693d-417fe81b19ee@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=akpm@linux-foundation.org \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.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
all inboxes | Powered by JetHome®