From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Allwinner drivers additions for 3.18
Date: Fri, 26 Sep 2014 17:16:25 +0200 [thread overview]
Message-ID: <20140926151625.GV15315@lukather> (raw)
In-Reply-To: <20140925191800.5855cef6@linux.lan.towertech.it>
On Thu, Sep 25, 2014 at 07:18:00PM +0200, Alessandro Zummo wrote:
> On Thu, 25 Sep 2014 18:31:03 +0200
> Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
>
> > Plus, this thread from last december
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2013-December/220778.html,
> > clearly showed that it's nothing new, and that Alessandro doesn't
> > maintain any tree, hence why I ended up merging it.
>
> I review the drivers, when appropriate, and Andrew thankfully picks them up.
> Important emails will usually get my attention. Even if I do not answer,
> is always a good idea to post in the mailing list, as there are a lot
> of competent people there.
Then may I suggest adding Andrew to the maintainers? Because if you
follow get_maintainers.pl right now, it only states that you are the
maintainer. That strongly implies that you should be the one doing
reviews, and we should at least wait for your Acked-by in order to
merge any RTC patches. And past experience show that we can wait for a
while.
Don't get this wrong, but the way you maintain it is rather unusual,
and your silence about this just makes us wonder what to do with your
patches, up until completely merging them anyway. For the record, it's
something I feel rather uncomfortable about, but it seems like it's
the only way to get something merged anyway.
Not having time to maintain your subsystem is totally fine, and as a
hobbyist maintainer too, I completely understand it. But if you can't
cope with the patches anymore, maybe you should find another
co-maintainer? Especially if you have reliable contributors, like
you're suggesting.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140926/a840a172/attachment-0001.sig>
next prev parent reply other threads:[~2014-09-26 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-20 20:28 [GIT PULL] Allwinner drivers additions for 3.18 Maxime Ripard
2014-09-25 16:20 ` Arnd Bergmann
2014-09-25 16:31 ` Maxime Ripard
2014-09-25 17:04 ` Arnd Bergmann
2014-09-26 15:04 ` Maxime Ripard
2014-09-25 17:18 ` Alessandro Zummo
2014-09-26 15:16 ` Maxime Ripard [this message]
2014-09-26 15:24 ` Alessandro Zummo
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=20140926151625.GV15315@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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