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=-3.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS autolearn=no 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 D3BA3C4332E for ; Thu, 19 Mar 2020 10:53:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AD61120753 for ; Thu, 19 Mar 2020 10:53:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=amarulasolutions.com header.i=@amarulasolutions.com header.b="SP1ghtcx" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727078AbgCSKxi (ORCPT ); Thu, 19 Mar 2020 06:53:38 -0400 Received: from mail-il1-f196.google.com ([209.85.166.196]:39609 "EHLO mail-il1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727065AbgCSKxi (ORCPT ); Thu, 19 Mar 2020 06:53:38 -0400 Received: by mail-il1-f196.google.com with SMTP id w15so1775228ilq.6 for ; Thu, 19 Mar 2020 03:53:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amarulasolutions.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mGv6o90nBAkHN8tZGMFBnMPu1+vfJLDuM2IfjimqHmY=; b=SP1ghtcxKDm86Nrinun/aUTKmLh8YvxfNs09WDEPx7kOtKCkXKDhc4YR8iqRTOp/gS 8P5efpzV/FxasWeGMas6yKVOjmZHlN/U7Vcs0aJQgCFwJkVeQ69oXJHMx4/FdNA71uX6 wqH9xxtU1P3ClcNJRgAKlGJ0idpOlYBjlQ2nM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mGv6o90nBAkHN8tZGMFBnMPu1+vfJLDuM2IfjimqHmY=; b=s3vmFSTr5ShHd/UpGpdKWDF60tYu8f6RU+WTkinyY4FAiUtSJ1LP6VtR+zJVek9uGM q9zoXw80MC9UZmW3sxEJ+LgYRmyuBkCL7zvzUFxz57TRykcjr+2R/mbHxuWgYV1HWaMA ez781n+lS/RFblXteLMEOeQZW2nJJikWWFJXt7z+fg3ku9+ZIJshbwtUuoCvMBg7Ecq6 usd/nPGk+f+JotvqRqjGkzSM/GKRCfMIjjDDyKpWjuyjJTCzYvRb4tZzDLvyYpBKPYJg hzd7T2oBv5brCdHhkegbdSDxvF9wkS7LrlTj/v6rSzgtjFjIzrRiBAjWiDh19Mo4ZdvO XqFQ== X-Gm-Message-State: ANhLgQ3ECZDyvnyP5g9JCHfJjmENOIJCWhIqL8Ifd31jB6cdtcNpnugE EAxgnhxgcy27MS5znJgLA2WPM0U6ajf06lWHvMOeIw== X-Google-Smtp-Source: ADFU+vsvDXUclE/dotigec15em503ixvkYRgAZl9akg13dIVS4KGv/OyL1NGUG/SO0ckE6T2Lmn93e+sS5SELs6oRrU= X-Received: by 2002:a92:77c2:: with SMTP id s185mr1287803ilc.297.1584615215203; Thu, 19 Mar 2020 03:53:35 -0700 (PDT) MIME-Version: 1.0 References: <20200318171003.5179-1-jagan@amarulasolutions.com> <20200318171003.5179-3-jagan@amarulasolutions.com> <20200318185814.GB28092@ravnborg.org> <20200319103159.GA18744@ravnborg.org> In-Reply-To: <20200319103159.GA18744@ravnborg.org> From: Jagan Teki Date: Thu, 19 Mar 2020 16:23:24 +0530 Message-ID: Subject: Re: [PATCH v2 3/3] MAINTAINERS: Update feiyang, st7701 panel bindings converted as YAML To: Sam Ravnborg Cc: Thierry Reding , Rob Herring , Mark Rutland , devicetree , David Airlie , linux-kernel , dri-devel , linux-amarula Content-Type: text/plain; charset="UTF-8" Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Hi Sam, On Thu, Mar 19, 2020 at 4:02 PM Sam Ravnborg wrote: > > Hi Jagan. > On Thu, Mar 19, 2020 at 03:50:44PM +0530, Jagan Teki wrote: > > On Thu, Mar 19, 2020 at 12:28 AM Sam Ravnborg wrote: > > > > > > On Wed, Mar 18, 2020 at 10:40:03PM +0530, Jagan Teki wrote: > > > > The feiyang,fy07024di26a30d.txt and sitronix,st7701.txt has been > > > > converted to YAML schemas, update MAINTAINERS to match them again. > > > > > > > > Signed-off-by: Jagan Teki > > > > > > The patch is fine. > > > I just dislike we repeat the maintainer info in two places.. > > > > Since these are two different panels. and entry similar like other > > panels.do you look for single entry for both the panels? > My comment was related to the fact that we have maintainer entry in the > .yaml file, and in MAINTAINERS. > > Seems a waste to have a distributed and a centralized place for this. > So patches are fine in this respect. > And merging the two bindings would be very bad, they are not alike. Seems to be a valid point considering the redundant entry in two places, but the idea of maintainer entry in binding vs MAINTAINER file may be different in terms of usage, and knowing to public. the later part is pretty generic for people to know, and checkpatch to find. I may not be sure, but some experts can help here. Jagan.