[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7dde45e2-8e26-5051-dea6-da3566bb5e0e@i2se.com>
Date: Thu, 3 Jan 2019 16:56:15 +0100
From: Stefan Wahren <stefan.wahren@...e.com>
To: Eric Anholt <eric@...olt.net>,
Florian Fainelli <f.fainelli@...il.com>,
linux-watchdog@...r.kernel.org, devicetree@...r.kernel.org,
Guenter Roeck <linux@...ck-us.net>,
Wim Van Sebroeck <wim@...ux-watchdog.org>,
Lee Jones <lee.jones@...aro.org>,
Mark Rutland <mark.rutland@....com>,
Rob Herring <robh+dt@...nel.org>
Cc: linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
bcm-kernel-feedback-list@...adcom.com
Subject: Re: [PATCH v4 0/5] BCM2835 PM driver
Hi Eric,
Am 13.12.2018 um 00:51 schrieb Eric Anholt:
> v4 adds the system-power-controller node to the binding as requested
> by Stefan. No driver changes are added to make the power controller
> behavior optional yet, since it's really unrelated to this series.
>
apologize for my late reply. This whole series is
Acked-by: Stefan Wahren <stefan.wahren@...e.com>
I would take care of the power controller behavior with an incremental
patch.
Should i also make patches to add the driver to the relevant defconfigs
(bcm2835, multi_v7, arm64)?
Thanks
Stefan
Powered by blists - more mailing lists