From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932760AbbCPXwR (ORCPT ); Mon, 16 Mar 2015 19:52:17 -0400 Received: from mail-gw2-out.broadcom.com ([216.31.210.63]:26431 "EHLO mail-gw2-out.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932155AbbCPXwN (ORCPT ); Mon, 16 Mar 2015 19:52:13 -0400 X-IronPort-AV: E=Sophos;i="5.11,412,1422950400"; d="scan'208";a="59575251" Message-ID: <55076CA1.60007@broadcom.com> Date: Mon, 16 Mar 2015 16:52:01 -0700 From: Scott Branden User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Brian Norris CC: , Dmitry Torokhov , Anatol Pomazao , Ray Jui , "Corneliu Doban" , Jonathan Richardson , Florian Fainelli , =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , , , , Kevin Cernekee Subject: Re: [PATCH 2/3] Documentation: devicetree: add binding doc for Broadcom NAND controller References: <1425691129-1150-1-git-send-email-computersforpeace@gmail.com> <1425691129-1150-3-git-send-email-computersforpeace@gmail.com> <55076247.4070104@broadcom.com> <20150316233706.GL32500@ld-irv-0074> <550769DD.2020208@broadcom.com> <20150316234634.GN32500@ld-irv-0074> In-Reply-To: <20150316234634.GN32500@ld-irv-0074> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Brian, On 15-03-16 04:46 PM, Brian Norris wrote: > On Mon, Mar 16, 2015 at 04:40:13PM -0700, Scott Branden wrote: >> >> On 15-03-16 04:37 PM, Brian Norris wrote: >>> On Mon, Mar 16, 2015 at 04:07:51PM -0700, Scott Branden wrote: >>> So, what's the standard? Company prefix? Long name? Commas? Hyphens? >> >> The problem with devicetree binding is there is no standard for much >> of anything. Some others use the vendor prefix for all their >> binding documentation. We can try to do the same? > > Ok, but we already have 3 versions for Broadcom. I can use 'brcm,' if > that helps... Yes, it helps if we try standardizing on the brcm vendor prefix in Documentation/devicetree/bindings/vendor-prefixes.txt. If you sift through the bindings directory you will find some of the other vendors have done the same. Also, of note. In Documentation/devicetree/bindings/submitting-patches.txt it states the Documentation should be the first patch in the series. Perhaps this helps the devicetree maintainer in reviewing bindings? Scott > > Brian >