Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Mediatek basic support for v3.17
Date: Tue, 15 Jul 2014 17:17:34 +0200	[thread overview]
Message-ID: <14060966.Jhk08lR3XI@wuerfel> (raw)
In-Reply-To: <20140715135913.GA18571@kroah.com>

On Tuesday 15 July 2014 06:59:13 Greg KH wrote:
> On Tue, Jul 15, 2014 at 01:11:42PM +0200, Matthias Brugger wrote:
> > The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:
> > 
> >   Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)
> > 
> > are available in the git repository at:
> > 
> >   https://github.com/mbgg/linux-mediatek.git tags/v3.17-next-basic-support
> 
> As these are only 7 patches, why do a git pull?  And I know I can't take
> pull requests from github, I'm not sure what the rules are for the ARM
> SoC developers either...
> 
> Just send patches, it's easier that way.

We generally prefer pull requests, but patches also work for us.

However, one note about the text in the pull request: Matthias,
please always try to be explicit about who you want to pull or
merge things when you are ready and list in the pull request the
other maintainers that have agreed to merging it (or whether they
have not sent an Ack yet, which is even more important).

In this case, the clocksource driver needs an Ack from the clocksource
maintainers, and the drivers/of/address.c changes need an Ack from the
OF maintainers. I assume you have those, but I'd have to first look
at the patches to be sure.

	arnd

  reply	other threads:[~2014-07-15 15:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 11:11 [GIT PULL] Mediatek basic support for v3.17 Matthias Brugger
2014-07-15 13:59 ` Greg KH
2014-07-15 15:17   ` Arnd Bergmann [this message]
2014-07-16 13:47     ` Matthias Brugger
2014-07-16 14:40       ` Rob Herring
2014-07-18  9:48         ` Matthias Brugger

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=14060966.Jhk08lR3XI@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