From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jesper Nilsson <jespern@axis.com>,
linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
"open list:ARM/ARTPEC MACHINE SUPPORT"
<linux-arm-kernel@axis.com>,
open list <linux-kernel@vger.kernel.org>,
Niklas Cassel <niklass@axis.com>,
Rob Herring <robh+dt@kernel.org>, Lars Persson <larper@axis.com>
Subject: Re: [GIT PULL]: ARM ARTPEC changes for 4.10
Date: Mon, 28 Nov 2016 14:51:11 +0100 [thread overview]
Message-ID: <20161128135111.GP19016@axis.com> (raw)
In-Reply-To: <10339600.mZlnsf0Sve@wuerfel>
On Mon, Nov 28, 2016 at 01:57:10PM +0100, Arnd Bergmann wrote:
> On Monday, November 28, 2016 1:33:31 PM CET Jesper Nilsson wrote:
> > > Hi Jesper and Niklas,
> > >
> > > I just found the old pull request while going through my mail backlog.
> > >
> > > A few things for you to remember for next time:
> > >
> > > - please send pull requests "To: arm@kernel.org" so we know they
> > > are destined for arm-soc
> >
> > Ok, should we add that in the MAINTAINERS file so we can
> > get it automatically from get_maintainer?
>
> No, we don't want to get every single patch that people submit to
> platform maintainers, only the consolidated pull requests that you
> send.
Right, sounds reasonable, will do.
> Arnd
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@axis.com
prev parent reply other threads:[~2016-11-28 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 15:09 [GIT PULL]: ARM ARTPEC changes for 4.10 Jesper Nilsson
2016-11-25 23:16 ` Arnd Bergmann
2016-11-28 12:33 ` Jesper Nilsson
2016-11-28 12:57 ` Arnd Bergmann
2016-11-28 13:51 ` Jesper Nilsson [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=20161128135111.GP19016@axis.com \
--to=jesper.nilsson@axis.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=jespern@axis.com \
--cc=larper@axis.com \
--cc=linux-arm-kernel@axis.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=niklass@axis.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).