linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL]: ARM ARTPEC changes for 4.10
Date: Mon, 28 Nov 2016 13:57:10 +0100	[thread overview]
Message-ID: <10339600.mZlnsf0Sve@wuerfel> (raw)
In-Reply-To: <20161128123331.GO19016@axis.com>

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 at 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.

	Arnd

  reply	other threads:[~2016-11-28 12:57 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 [this message]
2016-11-28 13:51       ` Jesper Nilsson

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=10339600.mZlnsf0Sve@wuerfel \
    --to=arnd@arndb.de \
    --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;
as well as URLs for NNTP newsgroup(s).