From: Eric Anholt <eric@anholt.net>
To: Florian Fainelli <f.fainelli@gmail.com>,
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 2/2] bcm2835-drivers-next-2019-03-04
Date: Fri, 08 Mar 2019 13:07:58 -0800 [thread overview]
Message-ID: <87ef7h3wi9.fsf@anholt.net> (raw)
In-Reply-To: <f07ce14b-53be-623e-deeb-d968745c31b4@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
Florian Fainelli <f.fainelli@gmail.com> writes:
> On 3/4/19 4:02 PM, Eric Anholt wrote:
>> The following changes since commit e1dc2b2e1bef7237fd8fc055fe1ec2a6ff001f91:
>>
>> ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware. (2019-02-01 10:34:32 +0100)
>>
>> are available in the Git repository at:
>>
>> git://github.com/anholt/linux tags/bcm2835-drivers-next-2019-03-04
>>
>> for you to fetch changes up to 4deabfae643d8852c643664d9088a647abfaa5d0:
>>
>> soc: bcm: bcm2835-pm: Fix error paths of initialization. (2019-03-04 15:33:14 -0800)
>>
>> ----------------------------------------------------------------
>> This pull request brings in two fixes for the new native bcm2835 power
>> domains driver.
>>
>> ----------------------------------------------------------------
>
> Looks like Stefan found an arm64 build configuration that failed linking
> with the driver, do you want to add an additional fix to this pull
> request that addresses that?
Took a look at it now, sent a fix.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-03-08 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 0:02 [GIT PULL 1/2] bcm2835-dt-next-2019-03-04 Eric Anholt
2019-03-05 0:02 ` [GIT PULL 2/2] bcm2835-drivers-next-2019-03-04 Eric Anholt
2019-03-08 18:05 ` Florian Fainelli
2019-03-08 21:07 ` Eric Anholt [this message]
2019-03-09 22:01 ` [GIT PULL 1/2] bcm2835-dt-next-2019-03-04 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=87ef7h3wi9.fsf@anholt.net \
--to=eric@anholt.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--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).