mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 2/2] bcm2835-drivers-next-2019-02-01
Date: Fri, 1 Feb 2019 11:29:55 -0800	[thread overview]
Message-ID: <ef786ac9-cd5f-6ddd-d8f6-3f947743d0e2@gmail.com> (raw)
In-Reply-To: <1549049054-5460-2-git-send-email-stefan.wahren@i2se.com>

On 2/1/19 11:24 AM, Stefan Wahren wrote:
> Hi Florian,
> 
> The following changes since commit f494caa480f7089ff9bba16dd865e190cee7e545:
> 
>   soc: bcm: Make PM driver default for BCM2835 (2019-01-24 19:19:22 +0100)
> 
> are available in the git repository at:
> 
>   git://github.com/anholt/linux tags/bcm2835-drivers-next-2019-02-01
> 
> for you to fetch changes up to e1dc2b2e1bef7237fd8fc055fe1ec2a6ff001f91:
> 
>   ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware. (2019-02-01 10:34:32 +0100)
> 
> ----------------------------------------------------------------
> This pull requests adds the missing devicetree parts for the
> new BCM2835 PM driver which depends on the driver changes.
> 
> -------------------------------------------------

Thanks for the quick turn around Stefan. Do you want this applied on top
of the previous drivers pull request you submitted, or as a replacement?

> 
> Eric Anholt (2):
>       ARM: bcm283x: Extend the WDT DT node out to cover the whole PM block. (v4)
>       ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware.
> 


-- 
Florian

      reply	other threads:[~2019-02-01 19:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01 19:24 [GIT PULL 1/2] bcm2835-dt-next-2019-02-01 Stefan Wahren
2019-02-01 19:24 ` [GIT PULL 2/2] bcm2835-drivers-next-2019-02-01 Stefan Wahren
2019-02-01 19:29   ` 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=ef786ac9-cd5f-6ddd-d8f6-3f947743d0e2@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