All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Stefan Wahren <wahrenst@gmx.net>,
	Florian Fainelli <f.fainelli@gmail.com>
Cc: Eric Anholt <eric@anholt.net>,
	linux-kernel@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/3] bcm2835-dt-next-2019-10-15
Date: Fri, 18 Oct 2019 10:20:21 -0700	[thread overview]
Message-ID: <a962dde6-7dc1-1bc1-5da3-d8822799c51b@gmail.com> (raw)
In-Reply-To: <1571159725-5090-1-git-send-email-wahrenst@gmx.net>

On 10/15/19 10:15 AM, Stefan Wahren wrote:
> Hi Florian,
> 
> The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
> 
>   Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
> 
> are available in the git repository at:
> 
>   git://github.com/anholt/linux tags/bcm2835-dt-next-2019-10-15
> 
> for you to fetch changes up to 46fdee06aeefedfc62a4c33b2c4a7a74682ac755:
> 
>   arm64: dts: broadcom: Add reference to RPi 4 B (2019-10-10 19:14:28 +0200)
> 
> ----------------------------------------------------------------
> This pull request introduce initial Raspberry Pi 4 support. But all the fancy
> stuff like GENET, PCIe, xHCI, 40 bit DMA and V3D is missing.
> 
> ----------------------------------------------------------------
> Stefan Wahren (7):
>       ARM: dts: bcm283x: Remove simple-bus from fixed clocks
>       ARM: dts: bcm283x: Remove brcm,bcm2835-pl011 compatible
>       ARM: dts: bcm283x: Move BCM2835/6/7 specific to bcm2835-common.dtsi
>       dt-bindings: arm: Convert BCM2835 board/soc bindings to json-schema
>       dt-bindings: arm: bcm2835: Add Raspberry Pi 4 to DT schema
>       ARM: dts: Add minimal Raspberry Pi 4 support
>       arm64: dts: broadcom: Add reference to RPi 4 B

Merged into devicetree/next, thanks Stefan.
-- 
Florian

WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: Stefan Wahren <wahrenst@gmx.net>,
	Florian Fainelli <f.fainelli@gmail.com>
Cc: Eric Anholt <eric@anholt.net>,
	bcm-kernel-feedback-list@broadcom.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/3] bcm2835-dt-next-2019-10-15
Date: Fri, 18 Oct 2019 10:20:21 -0700	[thread overview]
Message-ID: <a962dde6-7dc1-1bc1-5da3-d8822799c51b@gmail.com> (raw)
In-Reply-To: <1571159725-5090-1-git-send-email-wahrenst@gmx.net>

On 10/15/19 10:15 AM, Stefan Wahren wrote:
> Hi Florian,
> 
> The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
> 
>   Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
> 
> are available in the git repository at:
> 
>   git://github.com/anholt/linux tags/bcm2835-dt-next-2019-10-15
> 
> for you to fetch changes up to 46fdee06aeefedfc62a4c33b2c4a7a74682ac755:
> 
>   arm64: dts: broadcom: Add reference to RPi 4 B (2019-10-10 19:14:28 +0200)
> 
> ----------------------------------------------------------------
> This pull request introduce initial Raspberry Pi 4 support. But all the fancy
> stuff like GENET, PCIe, xHCI, 40 bit DMA and V3D is missing.
> 
> ----------------------------------------------------------------
> Stefan Wahren (7):
>       ARM: dts: bcm283x: Remove simple-bus from fixed clocks
>       ARM: dts: bcm283x: Remove brcm,bcm2835-pl011 compatible
>       ARM: dts: bcm283x: Move BCM2835/6/7 specific to bcm2835-common.dtsi
>       dt-bindings: arm: Convert BCM2835 board/soc bindings to json-schema
>       dt-bindings: arm: bcm2835: Add Raspberry Pi 4 to DT schema
>       ARM: dts: Add minimal Raspberry Pi 4 support
>       arm64: dts: broadcom: Add reference to RPi 4 B

Merged into devicetree/next, thanks Stefan.
-- 
Florian

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-10-18 17:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 17:15 [GIT PULL 1/3] bcm2835-dt-next-2019-10-15 Stefan Wahren
2019-10-15 17:15 ` Stefan Wahren
2019-10-15 17:15 ` [GIT PULL 2/3] bcm2835-soc-next-2019-10-15 Stefan Wahren
2019-10-15 17:15   ` Stefan Wahren
2019-10-18 17:22   ` Florian Fainelli
2019-10-18 17:22     ` Florian Fainelli
2019-12-14 10:54   ` BUG - was: " H. Nikolaus Schaller
2019-12-14 10:54     ` H. Nikolaus Schaller
2019-12-14 12:59     ` Russell King - ARM Linux admin
2019-12-14 12:59       ` Russell King - ARM Linux admin
2019-12-14 12:59       ` Russell King - ARM Linux admin
2019-12-14 15:54       ` [Letux-kernel] " Andreas Kemnade
2019-12-14 15:54         ` Andreas Kemnade
2019-12-14 16:54     ` Stefan Wahren
2019-12-14 16:54       ` Stefan Wahren
2019-12-14 16:54       ` Stefan Wahren
2019-12-14 20:02       ` H. Nikolaus Schaller
2019-12-14 20:02         ` H. Nikolaus Schaller
2019-12-14 20:02         ` H. Nikolaus Schaller
2019-10-15 17:15 ` [GIT PULL 3/3] bcm2835-maintainers-next-2019-10-15 Stefan Wahren
2019-10-15 17:15   ` Stefan Wahren
2019-10-18 17:21   ` Florian Fainelli
2019-10-18 17:21     ` Florian Fainelli
2019-10-18 17:20 ` Florian Fainelli [this message]
2019-10-18 17:20   ` [GIT PULL 1/3] bcm2835-dt-next-2019-10-15 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=a962dde6-7dc1-1bc1-5da3-d8822799c51b@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=eric@anholt.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=wahrenst@gmx.net \
    /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.