From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL][for 3.17] pull request for adding Hisilicon SoC MAINTAINERS
Date: Sat, 26 Jul 2014 09:41:53 -0700 [thread overview]
Message-ID: <20140726164153.GA25370@quad.lixom.net> (raw)
In-Reply-To: <6537586.3oPDKE8ex5@wuerfel>
On Sat, Jul 26, 2014 at 12:33:48PM +0200, Arnd Bergmann wrote:
> On Friday 25 July 2014 13:59:17 xuwei wrote:
> > Hi Olof, Hi Kevin, Hi Arnd,
> >
> > Resend it again and add arm at kernel.org into the CC list.
> > Please help to merge pull request for adding Hisilicon SoC maintainer.
> >
>
> Merged into next/soc, thanks!
>
> I think Olof's previous comment was that this didn't need to be
> a separate pull request but could just be part of the "pull
> request for hisilicon soc".
In particular, it seemed early to me to merge a maintainer update for a new
contributor that we haven't seen code from yet, and the pull requests we've
seen have been problematic. More often we label maintainers after they've
gotten used to the role.
It just seemed backwards the way it came in.
-Olof
prev parent reply other threads:[~2014-07-26 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 5:59 [GIT PULL][for 3.17] pull request for adding Hisilicon SoC MAINTAINERS xuwei
2014-07-26 10:33 ` Arnd Bergmann
2014-07-26 16:41 ` Olof Johansson [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=20140726164153.GA25370@quad.lixom.net \
--to=olof@lixom.net \
--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 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.