From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8030BC43381 for ; Mon, 1 Apr 2019 23:04:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4CD482084B for ; Mon, 1 Apr 2019 23:04:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=onstation.org header.i=@onstation.org header.b="fne9ZgrA" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728644AbfDAXEI (ORCPT ); Mon, 1 Apr 2019 19:04:08 -0400 Received: from onstation.org ([52.200.56.107]:38884 "EHLO onstation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725867AbfDAXEH (ORCPT ); Mon, 1 Apr 2019 19:04:07 -0400 Received: from localhost (c-98-239-145-235.hsd1.wv.comcast.net [98.239.145.235]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: masneyb) by onstation.org (Postfix) with ESMTPSA id 1947345704; Mon, 1 Apr 2019 23:04:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=onstation.org; s=default; t=1554159846; bh=7AyY+FyTUNeXSEdZNkzyrC00jxZWcA9wEIZppoRU5Q0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=fne9ZgrAYmANubUCDImJq+vW8c+48NK94LVCrKs/IzOdycCAPLiMguMLXCSXsJJMe GI5v2vaMWYe6mAHBj4vxvQhog5J//3cQ3L7WQW89tPcQITULyBVHYC8KmsLpYbDzU8 9QKkT7cgFJHsnIcleglx/P7at2pA/8XjcUl8K4Vw= Date: Mon, 1 Apr 2019 19:04:05 -0400 From: Brian Masney To: Pavel Machek Cc: lee.jones@linaro.org, daniel.thompson@linaro.org, jingoohan1@gmail.com, robh+dt@kernel.org, jacek.anaszewski@gmail.com, mark.rutland@arm.com, b.zolnierkie@samsung.com, dri-devel@lists.freedesktop.org, linux-leds@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org, dmurphy@ti.com, jonathan@marek.ca Subject: Re: [PATCH v2 2/3] dt-bindings: backlight: add lm3630a bindings Message-ID: <20190401230405.GA7877@basecamp> References: <20190401103034.21062-1-masneyb@onstation.org> <20190401103034.21062-3-masneyb@onstation.org> <20190401213926.GD14681@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190401213926.GD14681@amd> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 01, 2019 at 11:39:26PM +0200, Pavel Machek wrote: > On Mon 2019-04-01 06:30:33, Brian Masney wrote: > > Add new backlight bindings for the TI LM3630A dual-string white LED. > > > > Signed-off-by: Brian Masney > > --- > > .../leds/backlight/lm3630a-backlight.yaml | 112 > ++++++++++++++++++ > > What is that? Is it future of all the bindings? > > Up to device tree people, I guess, but... Yes, this is the future format of the bindings so that automated validation can be performed. See Documentation/devicetree/writing-schema.md. Brian