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:   Thu, 20 Sep 2018 13:09:52 +0100
From:   Alan Cox <gnomes@...rguk.ukuu.org.uk>
To:     Brian Dodge <bdodge09@...il.com>
Cc:     devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: arc vendor prefix

On Tue, 18 Sep 2018 21:05:20 -0400
Brian Dodge <bdodge09@...il.com> wrote:

> Hi,
> 
> In the linux kernel commit 91ab076e3a2f092254fe5231bbfa92b37fd52e38 the 
> vendor prefix "arctic" was added to vendor-prefixes.txt.
> 
> The original change I authored used "arc" not "arctic", and the device 
> tree bindings were added assuming that prefix in commit 
> ce9d22573d85341c987f997461ac712e4dbe47b1
> 
> Perhaps odeju changed the name to arctic in the patch after I created it 
> and before it was approved.
> 
> This pairing isn't really compatible is it?  Either the prefix should be 
> reverted to "arc" or the bindings (and driver source) changed to use 
> "arctic", as in "arctic,arc2c0608" vs. "arc,arc2c0608"

ARC is a Synopsys registered trademark for the ARC processor line. I'm not
sure what the right answer is but I think it might be better to keep to
arctic to avoid confusion with arc based products.

Alan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ