linux-kernel - Re: [PATCH RESEND 1/2] dt-bindings: phy: drop #clock-cells from rockchip,px30-dsi-dphy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 20 Dec 2019 16:51:28 +0530
From:   Kishon Vijay Abraham I <kishon@...com>
To:     Heiko Stübner <heiko@...ech.de>,
        Rob Herring <robh@...nel.org>
CC:     <robh+dt@...nel.org>, <mark.rutland@....com>,
        <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-rockchip@...ts.infradead.org>,
        Heiko Stuebner <heiko.stuebner@...obroma-systems.com>
Subject: Re: [PATCH RESEND 1/2] dt-bindings: phy: drop #clock-cells from
 rockchip,px30-dsi-dphy



On 16/12/19 11:31 pm, Heiko Stübner wrote:
> Hi Rob,
> 
> Am Montag, 16. Dezember 2019, 18:56:15 CET schrieb Rob Herring:
>> On Mon, 16 Dec 2019 13:24:47 +0100, Heiko Stuebner wrote:
>>> From: Heiko Stuebner <heiko.stuebner@...obroma-systems.com>
>>>
>>> Further review of the dsi components for the px30 revealed that the
>>> phy shouldn't expose the pll as clock but instead handle settings
>>> via phy parameters.
>>>
>>> As the phy binding is new and not used anywhere yet, just drop them
>>> so they don't get used.
>>>
>>> Fixes: 3817c7961179 ("dt-bindings: phy: add yaml binding for rockchip,px30-dsi-dphy")
>>> Signed-off-by: Heiko Stuebner <heiko.stuebner@...obroma-systems.com>
>>> ---
>>> Hi Kishon,
>>>
>>> maybe suitable as a fix for 5.5-rc?
>>>
>>> Thanks
>>> Heiko
>>>
>>>  .../devicetree/bindings/phy/rockchip,px30-dsi-dphy.yaml      | 5 -----
>>>  1 file changed, 5 deletions(-)
>>>
>>
>> Please add Acked-by/Reviewed-by tags when posting new versions. However,
>> there's no need to repost patches *only* to add the tags. The upstream
>> maintainer will do that for acks received on the version they apply.
>>
>> If a tag was not added on purpose, please state why and what changed.
> 
> sorry about that. The original response somehow did not thread correctly
> in my mail client, probably some fault on my side, so I've only found your
> mail just now by digging hard.
> 
> @Kishon, the original mail already got an
> 
> Acked-by: Rob Herring <robh@...nel.org>

merged now, Thanks!

-Kishon