public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] Broadcom devicetree changes for 4.16
Date: Thu, 4 Jan 2018 22:30:34 -0800	[thread overview]
Message-ID: <20180105063034.ixd3x6okkzt5l62z@localhost> (raw)
In-Reply-To: <20171222001227.30625-1-f.fainelli@gmail.com>

On Thu, Dec 21, 2017 at 04:12:26PM -0800, Florian Fainelli wrote:
> The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
> 
>   Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
> 
> are available in the git repository at:
> 
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.16/devicetree
> 
> for you to fetch changes up to ececb5639c33a6a0444bd8e1cda8bf2ef20c6a6b:
> 
>   Merge tag 'bcm2835-dt-next-2017-12-19' into devicetree/next (2017-12-20 17:32:58 -0800)
> 
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM-based SoCs Device Tree changes for
> 4.16, please pull the following:
> 
> - Stefan updates the BCM283x DTS to make consistent use of the existing GPIO
>   defines for the polarity specifier
> 
> ----------------------------------------------------------------
> Florian Fainelli (1):
>       Merge tag 'bcm2835-dt-next-2017-12-19' into devicetree/next
> 
> Stefan Wahren (1):
>       ARM: dts: bcm283x: Use GPIO polarity defines consistently

Merged, thanks.


-Olof

      parent reply	other threads:[~2018-01-05  6:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22  0:12 [GIT PULL 1/2] Broadcom devicetree changes for 4.16 Florian Fainelli
2017-12-22  0:12 ` [GIT PULL 2/2] Broadcom drivers " Florian Fainelli
2018-01-05  6:34   ` Olof Johansson
2018-01-05  6:30 ` Olof Johansson [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=20180105063034.ixd3x6okkzt5l62z@localhost \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox