From: Florian Fainelli <f.fainelli@gmail.com>
To: Eric Anholt <eric@anholt.net>, Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [GIT PULL 1/4] bcm2835-dt-next-2018-07-03
Date: Mon, 9 Jul 2018 05:20:13 -0700 [thread overview]
Message-ID: <74756307-2c22-e7de-386f-fb819ba8e3ed@gmail.com> (raw)
In-Reply-To: <20180703200511.2725-1-eric@anholt.net>
On 07/03/2018 01:05 PM, Eric Anholt wrote:
> Hi Florian,
>
> The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
>
> Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
>
> are available in the Git repository at:
>
> git://github.com/anholt/linux tags/bcm2835-dt-next-2018-07-03
>
> for you to fetch changes up to 7503668f7287a359f234cd000f4ca8572e40677b:
>
> ARM: dts: bcm283x: Add Transposer block (2018-07-02 12:46:20 -0700)
>
> ----------------------------------------------------------------
> This pull request brings in a board DT for the Raspberry Pi Compute
> Module and its I/O board, the Pi3's PMU node, and the display's
> transposer block.
>
> ----------------------------------------------------------------
Merged, thanks Eric!
--
Florian
prev parent reply other threads:[~2018-07-09 12:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 20:05 [GIT PULL 1/4] bcm2835-dt-next-2018-07-03 Eric Anholt
2018-07-03 20:05 ` [GIT PULL 2/4] bcm2835-drivers-next-2018-07-03 Eric Anholt
2018-07-09 12:25 ` Florian Fainelli
2018-07-03 20:05 ` [GIT PULL 3/4] bcm2835-defconfig-next-2018-07-03 Eric Anholt
2018-07-09 12:25 ` Florian Fainelli
2018-07-03 20:05 ` [GIT PULL 4/4] bcm2835-defconfig-64-next-2018-07-03 Eric Anholt
2018-07-09 12:25 ` Florian Fainelli
2018-07-09 12:20 ` Florian Fainelli [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=74756307-2c22-e7de-386f-fb819ba8e3ed@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;
as well as URLs for NNTP newsgroup(s).