From: Florian Fainelli <f.fainelli@gmail.com>
To: Eric Anholt <eric@anholt.net>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [GIT PULL 2/4] bcm2835-dt-64-next-2016-11-18
Date: Mon, 21 Nov 2016 21:13:14 -0800 [thread overview]
Message-ID: <9b9c72d9-a8e8-d0b5-a9bf-ed327c81967b@gmail.com> (raw)
In-Reply-To: <20161118185835.14452-2-eric@anholt.net>
Le 18/11/2016 à 10:58, Eric Anholt a écrit :
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> https://github.com/anholt/linux tags/bcm2835-dt-64-next-2016-11-18
>
> for you to fetch changes up to a44e87b47148c6ee6b78509f47e6a15c0fae890a:
>
> ARM64: dts: bcm2837-rpi-3-b: remove incorrect pwr LED (2016-11-16 13:49:38 -0800)
>
> ----------------------------------------------------------------
> This pull request brings thermal support to the BCM2837 DT, and a few
> other fixes.
>
> In order to get the thermal node that we're adjusting the compatible
> string on, we have to merge in the bcm2835-dt-next branch.
Merged, thanks!
--
Florian
next prev parent reply other threads:[~2016-11-22 5:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 18:58 [GIT PULL 1/4] bcm2835-dt-next-2016-11-18 Eric Anholt
2016-11-18 18:58 ` [GIT PULL 2/4] bcm2835-dt-64-next-2016-11-18 Eric Anholt
2016-11-22 5:13 ` Florian Fainelli [this message]
2016-11-18 18:58 ` [GIT PULL 3/4] bcm2835-defconfig-next-2016-11-18 Eric Anholt
2016-11-22 5:21 ` Florian Fainelli
2016-11-18 18:58 ` [GIT PULL 4/4] bcm2835-defconfig-64-next-2016-11-18 Eric Anholt
2016-11-22 5:26 ` Florian Fainelli
2016-11-22 5:08 ` [GIT PULL 1/4] bcm2835-dt-next-2016-11-18 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=9b9c72d9-a8e8-d0b5-a9bf-ed327c81967b@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=swarren@wwwdotorg.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
all inboxes | Powered by JetHome®