linux-kernel - RE: [PATCH 1/3] dt-bindings: firmware: imx: Move system control into dt-binding headfile

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] [day] [month] [year] [list]

Message-ID: <DB3PR0402MB39167F9D8D3101FDA02E3077F5D30@DB3PR0402MB3916.eurprd04.prod.outlook.com>
Date:   Thu, 23 Apr 2020 15:39:24 +0000
From:   Anson Huang <anson.huang@....com>
To:     Amit Kucheria <amit.kucheria@...durent.com>
CC:     Shawn Guo <shawnguo@...nel.org>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        "kernel@...gutronix.de" <kernel@...gutronix.de>,
        Fabio Estevam <festevam@...il.com>,
        Zhang Rui <rui.zhang@...el.com>,
        Daniel Lezcano <daniel.lezcano@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Leonard Crestez <leonard.crestez@....com>,
        "linux@...pel-privat.de" <linux@...pel-privat.de>,
        Peng Fan <peng.fan@....com>,
        LKML <linux-kernel@...r.kernel.org>,
        lakml <linux-arm-kernel@...ts.infradead.org>,
        Linux PM list <linux-pm@...r.kernel.org>,
        dl-linux-imx <linux-imx@....com>
Subject: RE: [PATCH 1/3] dt-bindings: firmware: imx: Move system control into
 dt-binding headfile

Hi, Amit

> Subject: Re: [PATCH 1/3] dt-bindings: firmware: imx: Move system control into
> dt-binding headfile
> 
> On Thu, Apr 23, 2020 at 7:38 PM Anson Huang <Anson.Huang@....com>
> wrote:
> >
> > i.MX8 SoCs DTS file needs system control macro definitions, so move
> > them into dt-binding headfile.
> >
> > Signed-off-by: Anson Huang <Anson.Huang@....com>
> 
> Why am I seeing multiple versions of the same series?
> 
> You need to squash this series so that the swapping of the header file happens
> in a single patch otherwise compilation will break with only patch 1 applied.

The first version I sent is having command error by mistake and patch 1/3 is missing,
So I send it again.

Yes, I will squash this series, sometimes I was confused about the patch category, but
making it NOT break the bisect or build should be the most important factor.

Thanks,
Anson