Dinh, Apologies for the delay on this. On Tue, Jul 30, 2013 at 07:10:28AM +0100, David Gibson wrote: > On Sat, Jul 27, 2013 at 10:41:25PM -0600, Grant Likely wrote: > > On Fri, 26 Jul 2013 14:05:26 -0600, Stephen Warren <swarren@xxxxxxxxxxxxx> wrote: > > > On 07/26/2013 01:39 PM, dinguyen@xxxxxxxxxx wrote: > > > > > > > diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt > > > > > > > +altr Altera Corp. > > > > > > In the context of Marvel(?) wanting to change between a longer and > > > stock-ticker vendor name, there was some discussion re: whether we had > > > decided not to use stock tickers any more. Is there still consensus that > > > we should? If so, I have no problem with this patch, but I wanted to > > > make sure everyone was on the same page. > > > > Stock ticker names are just fine by me. But once set they should not > > change. > > The old recommendation from OF working group was that vendor prefixes > could be either ticker symbols in all caps (e.g. "AAPL"), or some > other string in lower case. > > We've mostly only used the second option. Given that all the vendor prefixes we have (even those that are based on stock-ticker symbols) are lower case, I'd be happier with the lower-case "altr" in the original patch. >From the sounds of it, no-one wants to push for "altera", and we already have bindings with "altr", so I guess "altr" it is: Acked-by: Mark Rutland <mark.rutland@xxxxxxx> I note that there are some bindings with "altr" and some with "ALTR", though "altr" is more common. It would be nice if the binding documents were updated mention "ALTR" being deprecated, but useful for compatibility, hopefully this will lead to less confusion in future. It would also be nice for the drivers dealing with "ALTR" to be updated to also support "altr" (without removing support for "ALTR"). Thanks, Mark. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
