On Wed, Feb 12, 2020 at 10:39:42AM +0100, Benedikt Spranger wrote: > On Mon, 10 Feb 2020 08:43:10 +0100 > Maxime Ripard <maxime@xxxxxxxxxx> wrote: > > > Vendor names are usually either the vendor name itself or the stock > > name, so you should really use linutronix here > > May you kindly enlighten me why? > > "lx" is used internaly and externaly in projects, publications, > contracts, etc. as common abbreviation by the Linutronix GmbH. > Therefore it was self-evident to use this abbreviation in the device > tree. Googling "linutronix lx" returns approximately 0 meaningful results, so it's really not "common", at least externally. "lx linux" doesn't return much either. > As I did not found any documented rule in the kernel documentation, > which denote a restriction for the vendor abbreviation in the device > tree bindings the decision for "lx" was clear. It's in the devicetree specification: https://github.com/devicetree-org/devicetree-specification/releases/download/v0.2/devicetree-specification-v0.2.pdf Section 2.3: Standard Properties "The recommended format is "manufacturer,model", where manufacturer is a string describing the name of the manufacturer (such as a stock ticker symbol)" > A quick look into > "Documentation/devicetree/bindings/vendor-prefixes.yaml" > assured me in the decision to use "lx". > Here some example not fitting your rule: > "^ad,.*": > "^adi,.*": https://www.nasdaq.com/market-activity/stocks/adi > "^al,.*": > "^anvo,.*": That's the name of the company > ... > > In summary I would be encouraged if "lx" gets in, as it is *our* > abbreviation. How using the name of your company that *everybody* knows it by would be discouraging? Maxime
Attachment:
signature.asc
Description: PGP signature
