devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Rob Herring <robh@kernel.org>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	Chris Zhong <zyw@rock-chips.com>,
	Andrzej Hajda <a.hajda@samsung.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: Re: [PATCH v3 0/3] dt-bindings: display: convert panel bindings to DT Schema
Date: Fri, 10 Jul 2020 20:47:30 +0200	[thread overview]
Message-ID: <20200710184730.GA628995@ravnborg.org> (raw)
In-Reply-To: <20200709233502.GA1103707@bogus>

Hi Rob.

> > On Sat, Jul 04, 2020 at 12:28:03PM +0200, Sam Ravnborg wrote:
> > > This patch-set convert 3 of the remaining panel bindings to yaml.
> > > 
> > > This is a follow-up on v2 that converted a lot of panel bindings:
> > > https://lore.kernel.org/dri-devel/20200408195109.32692-1-sam@ravnborg.org/
> > > All was applied except for the reaming three patches included here.
> > > 
> > > One binding is a DSI binding so just added to panel-simple-dsi.
> > > The other two bindings addressed review feedback from Rob.
> > > 
> > > Sebastian Reichel has a pending patch to address the remaining
> > > panel binding in display/panel/
> > > 
> > > All bindings pass dt-binding-check.
> > > Based on top of drm-misc-next.
> > > 
> > > 	Sam
> > > 
> > > 
> > > Sam Ravnborg (3):
> > >       dt-bindings: display: convert innolux,p079zca to DT Schema
> > >       dt-bindings: display: convert samsung,s6e8aa0 to DT Schema
> > >       dt-bindings: display: convert sharp,lq101r1sx01 to DT Schema
> > 
> > git format-patch adds a space after the ',' - in the subject.
> > This is often a good idea, but not for binding files.
> > Will fix when I apply - if I do not forget that is..
> 
> Sure about that? I'm pretty sure it's dri-devel doing it. Look at 
> lore.kernel.org copies for different lists. I've been fighting with that 
> first in patchwork (which had this bug) and then in b4 (which is where 
> it got nailed down to dri-devel).
You are right.

The patches that I copied myself on had the correct subject.
Only the dri-devel mails had the mangled subject.

	Sam

> 
> Rob

  reply	other threads:[~2020-07-10 18:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-04 10:28 [PATCH v3 0/3] dt-bindings: display: convert panel bindings to DT Schema Sam Ravnborg
2020-07-04 10:28 ` [PATCH v3 1/3] dt-bindings: display: convert innolux,p079zca " Sam Ravnborg
2020-07-09 23:35   ` [PATCH v3 1/3] dt-bindings: display: convert innolux, p079zca " Rob Herring
2020-07-04 10:28 ` [PATCH v3 2/3] dt-bindings: display: convert samsung,s6e8aa0 " Sam Ravnborg
2020-07-09 23:36   ` [PATCH v3 2/3] dt-bindings: display: convert samsung, s6e8aa0 " Rob Herring
2020-07-04 10:28 ` [PATCH v3 3/3] dt-bindings: display: convert sharp,lq101r1sx01 " Sam Ravnborg
2020-07-04 10:34 ` [PATCH v3 0/3] dt-bindings: display: convert panel bindings " Sam Ravnborg
2020-07-09 23:35   ` Rob Herring
2020-07-10 18:47     ` Sam Ravnborg [this message]
2020-07-10 19:17 ` Sam Ravnborg

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=20200710184730.GA628995@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=a.hajda@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=robh@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --cc=thierry.reding@gmail.com \
    --cc=zyw@rock-chips.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 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).