linux-kernel - Re: [PATCH v1 2/4] dt-bindings: clock: mediatek: add g3dsys bindings

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]

Message-ID: <152415874117.46528.7501317526173019067@swboyd.mtv.corp.google.com>
Date:   Thu, 19 Apr 2018 10:25:41 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Sean Wang <sean.wang@...iatek.com>
Cc:     airlied@...ux.ie, devicetree@...r.kernel.org,
        linux-mediatek@...ts.infradead.org, mark.rutland@....com,
        matthias.bgg@...il.com, mturquette@...libre.com,
        robh+dt@...nel.org, dri-devel@...ts.freedesktop.org,
        linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 2/4] dt-bindings: clock: mediatek: add g3dsys bindings

Quoting Sean Wang (2018-04-18 20:50:02)
> On Wed, 2018-04-18 at 20:18 -0700, Stephen Boyd wrote:
> > Quoting sean.wang@...iatek.com (2018-04-18 03:24:54)
> > > From: Sean Wang <sean.wang@...iatek.com>
> > > 
> > > Add bindings to g3dsys providing necessary clock and reset control to
> > > Mali-450.
> > > 
> > > Signed-off-by: Sean Wang <sean.wang@...iatek.com>
> > > ---
> > >  .../bindings/arm/mediatek/mediatek,g3dsys.txt      | 30 ++++++++++++++++++++++
> > 
> > Why isn't this under bindings/clock/ ?
> > 
> 
> Tons of bindings for clock controller have been present at
> binding/arm/mediatek. g3dsys just have a follow-up to them.
> 
> It's worth another patch moving them all from bindings/arm/mediatek/ to
> bindings/clock/mediatek.
> 
> what's your opinion for either doing it prior to g3dsys binding being
> added or doing it in the future ?
> 

Doing it at a later time is fine. Just wondering why they're all getting
dumped into the arm/ directory.