linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: akpm@linux-foundation.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] MAINTAINERS: add myself as maintainer of fbdev
Date: Wed, 21 Dec 2016 17:50:05 +0100	[thread overview]
Message-ID: <1915709.xWflxUXmem@amdc3058> (raw)
In-Reply-To: <20161221150654.GA14815@sudip-tp>


Hi,

On Wednesday, December 21, 2016 03:06:55 PM Sudip Mukherjee wrote:
> On Thu, Dec 15, 2016 at 03:45:47PM +0100, Bartlomiej Zolnierkiewicz wrote:
> > I would like to help with fbdev maintenance.  I can dedicate some time
> > for reviewing and handling patches but won't have time for much more.
> > 
> 
> I thought usually someone takes over the maintainer role after
> proving that he cares for a subsystem for a certain period of time.
> 
> I know Bartlomiej is here for a long time, but fbdev??

I'm not a fbdev expert and I'm not pretending to be one.

I decided to officially handle patches for fbdev after this
subsystem has been marked as Orphan in upstream tree (nobody
has volunteered to take over from Tomi after he sent his
resignation patch to a list a week earlier).

I won't have a lot of time even for this activity so help is
very much welcomed.

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics

  reply	other threads:[~2016-12-21 16:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15 14:45 [PATCH] MAINTAINERS: add myself as maintainer of fbdev Bartlomiej Zolnierkiewicz
2016-12-21 15:06 ` Sudip Mukherjee
2016-12-21 16:50   ` Bartlomiej Zolnierkiewicz [this message]
2016-12-21 21:38     ` Sudip Mukherjee

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=1915709.xWflxUXmem@amdc3058 \
    --to=b.zolnierkie@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=tomi.valkeinen@ti.com \
    /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;
as well as URLs for NNTP newsgroup(s).