All of lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: BCM5301X: DT changes for v3.20
Date: Fri, 23 Jan 2015 14:01:11 -0800	[thread overview]
Message-ID: <20150123220111.GE20896@quad.lixom.net> (raw)
In-Reply-To: <54BED7D7.80207@hauke-m.de>

On Tue, Jan 20, 2015 at 11:33:59PM +0100, Hauke Mehrtens wrote:
> Hi Olof, Hi Arnd,
> 
> This is a pull request with some dt updates for BCM5301X for 3.20.
> 
> The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
> 
>   Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
> 
> are available in the git repository at:
> 
>   https://github.com/hauke/linux.git tags/bcm5301x-dt-2015-01-20
> 
> for you to fetch changes up to 5b1864b899d2b591402704dd0f6528c8661f1817:
> 
>   ARM: BCM5301X: Add DT for Buffalo WZR-900DHP (2015-01-20 23:23:25 +0100)

Hi Hauke,

I've merged this into next/dt now, comments below.

> 
> ----------------------------------------------------------------
> bcm5301x-dt-2015-01-20: ARM: BCM5301X: dts updates for 3.20
> 
> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>

No signed-off-by needed in the tag -- the fact that you have signed it is
enough. We do ask for a few words about what's in the branch though more than
"dts updates". Something to think about going forward.

Also:

We had asked that broadcom platforms go in together through Florian from
here on out, so we don't have to deal with merge requests from each and
every one of you since there are several subplatforms. Would that be ok
with you?


-Olof

  reply	other threads:[~2015-01-23 22:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 22:33 [GIT PULL] ARM: BCM5301X: DT changes for v3.20 Hauke Mehrtens
2015-01-23 22:01 ` Olof Johansson [this message]
2015-01-25  6:22   ` Florian Fainelli
2015-02-10  5:42     ` Florian Fainelli
2015-02-10 10:17       ` Olof Johansson
2015-02-28 23:13         ` Rafał Miłecki
2015-03-02 23:45           ` Florian Fainelli

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=20150123220111.GE20896@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.