From: Florian Fainelli <f.fainelli@gmail.com>
To: Stefan Wahren <stefan.wahren@i2se.com>,
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-01-29
Date: Thu, 31 Jan 2019 20:10:24 -0800 [thread overview]
Message-ID: <92b0b6d9-ced1-4a0a-e0d5-d72751dacfcb@gmail.com> (raw)
In-Reply-To: <1548788008-4733-1-git-send-email-stefan.wahren@i2se.com>
On 1/29/19 10:53 AM, Stefan Wahren wrote:
> Hi Florian,
>
> sorry for being that late and hoping it's not too late.
>
> The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
>
> Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
>
> are available in the git repository at:
>
> git://github.com/anholt/linux tags/bcm2835-dt-next-2019-01-29
>
> for you to fetch changes up to 14117e0af4a853b2b37925f526b2bfe1cfc7b285:
>
> ARM: dts: bcm2835-rpi-zero-w: Drop unnecessary pinctrl (2019-01-22 07:25:59 +0100)
>
> ----------------------------------------------------------------
> This pull request adds the necessary changes for the new BCM2835 PM driver,
> support for the new Raspberry Pi 3 A+ and the missing GPIO labels for RPi 2/3.
> Additionally it contains some minor DT fixes.
>
> ----------------------------------------------------------------
Merged into devicetree/next, thanks Stefan!
--
Florian
next prev parent reply other threads:[~2019-02-01 4:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 18:53 Stefan Wahren
2019-01-29 18:53 ` [GIT PULL 2/3] bcm2835-dt-64-next-2019-01-29 Stefan Wahren
2019-02-01 4:10 ` Florian Fainelli
2019-02-01 21:11 ` Florian Fainelli
2019-01-29 18:53 ` [GIT PULL 3/3] bcm2835-drivers-next-2019-01-29 Stefan Wahren
2019-02-01 4:11 ` Florian Fainelli
2019-02-01 4:10 ` Florian Fainelli [this message]
2019-02-01 5:02 ` [GIT PULL 1/3] bcm2835-dt-next-2019-01-29 Florian Fainelli
2019-02-01 11:15 ` Stefan Wahren
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=92b0b6d9-ced1-4a0a-e0d5-d72751dacfcb@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=stefan.wahren@i2se.com \
/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
Powered by JetHome