LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jagan Teki <jagan@amarulasolutions.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree <devicetree@vger.kernel.org>,
	David Airlie <airlied@linux.ie>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-amarula <linux-amarula@amarulasolutions.com>
Subject: Re: [PATCH v2 3/3] MAINTAINERS: Update feiyang, st7701 panel bindings converted as YAML
Date: Thu, 19 Mar 2020 16:23:24 +0530	[thread overview]
Message-ID: <CAMty3ZCjHALfw3Hws5A1M3jbjtkGgeerUZb-wnrppFtQ0dvpTg@mail.gmail.com> (raw)
In-Reply-To: <20200319103159.GA18744@ravnborg.org>

Hi Sam,

On Thu, Mar 19, 2020 at 4:02 PM Sam Ravnborg <sam@ravnborg.org> 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 <sam@ravnborg.org> 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 <jagan@amarulasolutions.com>
> > >
> > > 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.

  reply	other threads:[~2020-03-19 10:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 17:10 [PATCH v2 1/3] dt-bindings: display: panel: Convert feiyang,fy07024di26a30d to DT schema Jagan Teki
2020-03-18 17:10 ` [PATCH v2 2/3] dt-bindings: display: panel: Convert sitronix,st7701 " Jagan Teki
2020-03-25 19:16   ` Rob Herring
2020-03-18 17:10 ` [PATCH v2 3/3] MAINTAINERS: Update feiyang, st7701 panel bindings converted as YAML Jagan Teki
2020-03-18 18:58   ` Sam Ravnborg
2020-03-19 10:20     ` Jagan Teki
2020-03-19 10:31       ` Sam Ravnborg
2020-03-19 10:53         ` Jagan Teki [this message]
2020-03-18 18:57 ` [PATCH v2 1/3] dt-bindings: display: panel: Convert feiyang, fy07024di26a30d to DT schema Sam Ravnborg
2020-03-19 10:36   ` Jagan Teki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMty3ZCjHALfw3Hws5A1M3jbjtkGgeerUZb-wnrppFtQ0dvpTg@mail.gmail.com \
    --to=jagan@amarulasolutions.com \
    --cc=airlied@linux.ie \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sam@ravnborg.org \
    --cc=thierry.reding@gmail.com \
    --subject='Re: [PATCH v2 3/3] MAINTAINERS: Update feiyang, st7701 panel bindings converted as YAML' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).