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: <20180703230745.GA2129@rob-hp-laptop>
Date:   Tue, 3 Jul 2018 17:07:45 -0600
From:   Rob Herring <robh@...nel.org>
To:     Luis Araneda <luaraneda@...il.com>
Cc:     Michal Simek <michal.simek@...inx.com>,
        Mark Rutland <mark.rutland@....com>,
        devicetree <devicetree@...r.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 5/5] arm: dts: zynq: remove "zynq" prefix from
 compatible property

On Tue, Jul 03, 2018 at 03:18:49AM -0400, Luis Araneda wrote:
> Hi Michal,
> 
> On Thu, Jun 28, 2018 at 2:42 AM Michal Simek <michal.simek@...inx.com> wrote:
> > zynq name here is correct which is saying that hardblock is going to be
> > described. Without it it is suggesting that hardblock is not used and it
> > is for example on zybo with microblaze.
> 
> In my opinion, the zynq name is just adding redundant information to
> the "xlnx,zynq-7000" value.

Maybe so, but you can't just go around changing compatible strings. Once 
set, it's an ABI.

Rob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ