From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 9ECF5BF7 for ; Tue, 17 Oct 2017 13:49:10 +0000 (UTC) Received: from mail-pg0-f66.google.com (mail-pg0-f66.google.com [74.125.83.66]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E63FA4E8 for ; Tue, 17 Oct 2017 13:49:09 +0000 (UTC) Received: by mail-pg0-f66.google.com with SMTP id y7so1465160pgb.7 for ; Tue, 17 Oct 2017 06:49:09 -0700 (PDT) MIME-Version: 1.0 Sender: glikely@secretlab.ca In-Reply-To: <20171017114823.58476908@bbrezillon> References: <20171017114823.58476908@bbrezillon> From: Grant Likely Date: Tue, 17 Oct 2017 14:48:48 +0100 Message-ID: To: Boris Brezillon Content-Type: text/plain; charset="UTF-8" Cc: "devicetree@vger.kernel.org" , Kumar Gala , "ksummit-discuss@lists.linuxfoundation.org" , Rob Herring , devicetree-spec@vger.kernel.org, Pantelis Antoniou , Andy Gross , Lucas Stach , David Gibson Subject: Re: [Ksummit-discuss] Devicetree Workshop at Kernel Summit Prague (26 Oct 2017) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Oct 17, 2017 at 10:48 AM, Boris Brezillon wrote: > Hello Grant, > > On Mon, 9 Oct 2017 21:39:51 +0100 > Grant Likely wrote: > >> Kernel Summit is now just over 2 weeks away and it is time to pull >> together the schedule for the Devicetree workshop. Originally I >> planned on just an afternoon, but I've got the room for the whole day, >> so I've got a lot of flexibility on the schedule. Unscheduled time can >> be used for hacking. >> >> Date: 26 Oct 2017 >> Time: 9:00am-5:30pm (Lunch from 12:30-2:30) >> Location: Athens room - Hilton Prague >> >> If you plan to attend, make sure you update your OSSunmitE/ELCE >> registration to include the DT Workshop (log in to access and modify >> your registration): >> >> https://www.regonline.com/register/login.aspx?eventID=1883377&MethodId=0&EventsessionId=&Email_Address=&membershipID= >> >> Here is my current list of topics in no particular order, including >> the topic moderator: >> >> Runtime memory consumption (Rob Herring) >> Overlay maintenance plan (TBC) >> Stable ABI for devicetree (TBC) >> DT YAML encoding (Pantelis Antoniou) >> DT Schema format - option 1 (Pantelis Antoniou) >> DT Schema format - option 2 (Grant Likely) >> Sharing Generic bindings (TBC) >> devicetree.org update (Grant) >> >> Reply to this email if you want to propose another topic. > > Not sure yet if I'll attend the DT workshop or not, but I thought I > could ask my question here because it might be of interest to someone > else who is attending. > > What happens when the DT bindings is not documented in Linux but in an > another project because this project was the first to use it. > > I had the case here http://patchwork.ozlabs.org/patch/810275/, and I'm > not sure what's the policy when this happens. Should we add a file > under Documentation/devicetree/bindings/... that points to the external > doc file, should we duplicate the DT bindings doc in Linux, or should > we just leave the bindings undocumented in the kernel tree? I'm going to add this as a topic. I've got my own opinion, but it would be better to discuss in the room because it affects maintainers. g. > > Regards, > > Boris From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Likely Subject: Re: [Ksummit-discuss] Devicetree Workshop at Kernel Summit Prague (26 Oct 2017) Date: Tue, 17 Oct 2017 14:48:48 +0100 Message-ID: References: <20171017114823.58476908@bbrezillon> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20171017114823.58476908@bbrezillon> Sender: devicetree-spec-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Boris Brezillon Cc: "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "ksummit-discuss-cunTk1MwBs98uUxBSJOaYoYkZiVZrdSR2LY78lusg7I@public.gmane.org" , David Gibson , Julia Lawall , Pantelis Antoniou , Lucas Stach , Kumar Gala , Andy Gross , Rob Herring , Frank Rowand List-Id: devicetree@vger.kernel.org On Tue, Oct 17, 2017 at 10:48 AM, Boris Brezillon wrote: > Hello Grant, > > On Mon, 9 Oct 2017 21:39:51 +0100 > Grant Likely wrote: > >> Kernel Summit is now just over 2 weeks away and it is time to pull >> together the schedule for the Devicetree workshop. Originally I >> planned on just an afternoon, but I've got the room for the whole day, >> so I've got a lot of flexibility on the schedule. Unscheduled time can >> be used for hacking. >> >> Date: 26 Oct 2017 >> Time: 9:00am-5:30pm (Lunch from 12:30-2:30) >> Location: Athens room - Hilton Prague >> >> If you plan to attend, make sure you update your OSSunmitE/ELCE >> registration to include the DT Workshop (log in to access and modify >> your registration): >> >> https://www.regonline.com/register/login.aspx?eventID=1883377&MethodId=0&EventsessionId=&Email_Address=&membershipID= >> >> Here is my current list of topics in no particular order, including >> the topic moderator: >> >> Runtime memory consumption (Rob Herring) >> Overlay maintenance plan (TBC) >> Stable ABI for devicetree (TBC) >> DT YAML encoding (Pantelis Antoniou) >> DT Schema format - option 1 (Pantelis Antoniou) >> DT Schema format - option 2 (Grant Likely) >> Sharing Generic bindings (TBC) >> devicetree.org update (Grant) >> >> Reply to this email if you want to propose another topic. > > Not sure yet if I'll attend the DT workshop or not, but I thought I > could ask my question here because it might be of interest to someone > else who is attending. > > What happens when the DT bindings is not documented in Linux but in an > another project because this project was the first to use it. > > I had the case here http://patchwork.ozlabs.org/patch/810275/, and I'm > not sure what's the policy when this happens. Should we add a file > under Documentation/devicetree/bindings/... that points to the external > doc file, should we duplicate the DT bindings doc in Linux, or should > we just leave the bindings undocumented in the kernel tree? I'm going to add this as a topic. I've got my own opinion, but it would be better to discuss in the room because it affects maintainers. g. > > Regards, > > Boris