linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/7] Broadcom devicetree changes for 4.12
Date: Sun, 26 Mar 2017 00:33:15 +0300	[thread overview]
Message-ID: <20170325213315.7dw2nugvhumhypbn@tarshish> (raw)
In-Reply-To: <20170324175807.27272-2-f.fainelli@gmail.com>

Hi Florian,

On Fri, Mar 24, 2017 at 10:58:02AM -0700, Florian Fainelli wrote:
> The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:
> 
>   Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
> 
> are available in the git repository at:
> 
>   http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.12/devicetree
> 
> for you to fetch changes up to 414ce21ae20547e0eea72fe0c4e8ee3280d30888:
> 
>   Merge tag 'bcm2835-dt-next-2017-03-21' into devicetree/next (2017-03-24 10:12:31 -0700)
> 
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM-based SoCs Device Tree updates for
> 4.12, please pull the following:

What about my dts fixes that were in the delayed 4.11 pull request[1]?

[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2017-March/491554.html

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

  reply	other threads:[~2017-03-25 21:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24 17:58 [GIT PULL 1/7] Broadcom soc changes for 4.12 Florian Fainelli
2017-03-24 17:58 ` [GIT PULL 2/7] Broadcom devicetree " Florian Fainelli
2017-03-25 21:33   ` Baruch Siach [this message]
2017-03-27 17:14     ` Eric Anholt
2017-03-27 19:52       ` Florian Fainelli
2017-03-31 10:04   ` Arnd Bergmann
2017-03-24 17:58 ` [GIT PULL 3/7] Broadcom devicetree-arm64 " Florian Fainelli
2017-03-31  9:53   ` Arnd Bergmann
2017-03-24 17:58 ` [GIT PULL 4/7] Broadcom maintainers " Florian Fainelli
2017-03-31  8:56   ` Arnd Bergmann
2017-03-24 17:58 ` [GIT PULL 5/7] Broadcom defconfig " Florian Fainelli
2017-03-31  9:01   ` Arnd Bergmann
2017-03-24 17:58 ` [GIT PULL 6/7] Broadcom defconfig-arm64 " Florian Fainelli
2017-03-31  9:04   ` Arnd Bergmann
2017-03-24 17:58 ` [GIT PULL 7/7] Broadcom drivers " Florian Fainelli
2017-03-31  8:59   ` Arnd Bergmann
2017-03-30 15:29 ` [GIT PULL 1/7] Broadcom soc " Arnd Bergmann
2017-03-31  8:53   ` Arnd Bergmann

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=20170325213315.7dw2nugvhumhypbn@tarshish \
    --to=baruch@tkos.co.il \
    --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).