Re: [PATCH] of: add vendor prefix for Honeywell

[Olof Johansson]

On February 3, 2014 6:46:58 AM PST, Rob Herring <robherring2@xxxxxxxxx> wrote:
>On Fri, Jan 31, 2014 at 3:46 PM, Belisko Marek
><marek.belisko@xxxxxxxxx> wrote:
>> On Fri, Jan 31, 2014 at 7:53 PM, Olof Johansson <olof@xxxxxxxxx>
>wrote:
>>> On Sat, Jan 25, 2014 at 1:38 PM, Marek Belisko <marek@xxxxxxxxxxxxx>
>wrote:
>>>> Signed-off-by: Marek Belisko <marek@xxxxxxxxxxxxx>
>>>> ---
>>>>  Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
>>>>  1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
>b/Documentation/devicetree/bindings/vendor-prefixes.txt
>>>> index 3f900cd..b14c617 100644
>>>> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
>>>> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
>>>> @@ -40,6 +40,7 @@ gmt   Global Mixed-mode Technology, Inc.
>>>>  gumstix        Gumstix, Inc.
>>>>  haoyu  Haoyu Microelectronic Co. Ltd.
>>>>  hisilicon      Hisilicon Limited.
>>>> +honeywell      Honeywell
>>>
>>> The norm has usually been to use the the stock ticker symbol of a
>>> public company if it is available. In other words, I think the
>prefix
>>> here should be 'hon', since Honeywell is a publicly traded company
>>> under that ticker.
>> OK I didn't know about that. I just pick name from here:
>> Documentation/devicetree/bindings/iio/magnetometer/hmc5843.txt
>> So we need to update also compatible property in mentioned file.
>
>It appears this is already used in omap4-sdp dts for some time, so I'm
>inclined to leave it as honeywell to avoid breaking old dtbs.

Fair enough.

It would be good to find a way to avoid too much ambiguity around prefixes longer term but that's a discussion for another day.

-Olof


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/