From: Arnd Bergmann <arnd@arndb.de>
To: Axel Lin <axel.lin@ingics.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
arm@kernel.org
Subject: Re: [PATCH] soc: versatile: Add terminating entry for realview_soc_of_match
Date: Wed, 29 Oct 2014 09:01:59 +0100 [thread overview]
Message-ID: <2097592.uX1sdbECvl@wuerfel> (raw)
In-Reply-To: <CAFRkauAP9+6VM40O-WLMKY5X5WrpyrCqBhjwVbWGSV2B_+DPXg@mail.gmail.com>
On Wednesday 29 October 2014 08:48:11 Axel Lin wrote:
> >>
> >> Arnd are you merging this directly into ARM SoC?
> >>
> >
> > Applied to the fixes branch.
> Thanks.
> >
> > Please remember to add arm@kernel.org when you want us to pick up the
> > patches.
> scripts/get_maintainer.pl does not suggest arm@kernel.org for this patch.
>
> $ scripts/get_maintainer.pl
> 0001-soc-versatile-Add-terminating-entry-for-realview_soc.patch
> Linus Walleij <linus.walleij@linaro.org>
> (commit_signer:1/1=100%,authored:1/1=100%,added_lines:144/144=100%)
> Arnd Bergmann <arnd@arndb.de> (commit_signer:1/1=100%)
> linux-kernel@vger.kernel.org (open list)
>
> Maybe it needs update the maintainer entry?
We generally don't want developers other than subarch maintainers to
send us stuff directly and we certainly don't want to be Cc'd on
(literally, if you count every version in review) thousands of patches
per kernel release.
My comment was directed at Linus, who has sent us the updates for
vexpress recently and who was (rightfully) asking for the patch to
be picked up.
Arnd
prev parent reply other threads:[~2014-10-29 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 15:41 [PATCH] soc: versatile: Add terminating entry for realview_soc_of_match Axel Lin
2014-10-20 12:37 ` Linus Walleij
2014-10-28 21:05 ` Arnd Bergmann
2014-10-29 0:48 ` Axel Lin
2014-10-29 8:01 ` Arnd Bergmann [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=2097592.uX1sdbECvl@wuerfel \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=axel.lin@ingics.com \
--cc=linus.walleij@linaro.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