All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jagan Teki <jagan@amarulasolutions.com>
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 11:31:59 +0100	[thread overview]
Message-ID: <20200319103159.GA18744@ravnborg.org> (raw)
In-Reply-To: <CAMty3ZDhVfvYXV7OO+NT+d_2YHbsJXebzjdtYkqtdD+X=Ch0yQ@mail.gmail.com>

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.

	Sam

WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree <devicetree@vger.kernel.org>,
	David Airlie <airlied@linux.ie>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	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 11:31:59 +0100	[thread overview]
Message-ID: <20200319103159.GA18744@ravnborg.org> (raw)
In-Reply-To: <CAMty3ZDhVfvYXV7OO+NT+d_2YHbsJXebzjdtYkqtdD+X=Ch0yQ@mail.gmail.com>

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.

	Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

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

Thread overview: 20+ 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 1/3] dt-bindings: display: panel: Convert feiyang, fy07024di26a30d " Jagan Teki
2020-03-18 17:10 ` [PATCH v2 2/3] dt-bindings: display: panel: Convert sitronix,st7701 " 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   ` [PATCH v2 2/3] dt-bindings: display: panel: Convert sitronix,st7701 " Rob Herring
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 17:10   ` Jagan Teki
2020-03-18 18:58   ` Sam Ravnborg
2020-03-18 18:58     ` Sam Ravnborg
2020-03-19 10:20     ` Jagan Teki
2020-03-19 10:20       ` Jagan Teki
2020-03-19 10:31       ` Sam Ravnborg [this message]
2020-03-19 10:31         ` Sam Ravnborg
2020-03-19 10:53         ` Jagan Teki
2020-03-19 10:53           ` Jagan Teki
2020-03-18 18:57 ` [PATCH v2 1/3] dt-bindings: display: panel: Convert feiyang, fy07024di26a30d to DT schema Sam Ravnborg
2020-03-18 18:57   ` Sam Ravnborg
2020-03-19 10:36   ` Jagan Teki
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=20200319103159.GA18744@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=airlied@linux.ie \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jagan@amarulasolutions.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@gmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.