linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Benoit Parrot <bparrot@ti.com>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: correct entry in TI VPE/CAL DRIVERS section
Date: Sat, 1 Feb 2020 20:20:08 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.2002012018480.6548@felia> (raw)
In-Reply-To: <CAHp75Ve5gFF8R8i_ietRUi+sfy4nQi4MBzG4XnmJfJRqYH85wQ@mail.gmail.com>



On Sat, 1 Feb 2020, Andy Shevchenko wrote:

> On Sat, Feb 1, 2020 at 5:17 PM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
> >
> > perl scripts/parse-maintainers.pl complains:
> >
> > Odd non-pattern line '  Documentation/devicetree/bindings/media/ti,cal.yaml
> > ' for 'TI VPE/CAL DRIVERS' at scripts/parse-maintainers.pl line 147,
> > <$file> line 16742.
> >
> > Commit 2099ef02c6c0 ("media: dt-bindings: media: cal: convert binding to
> > yaml") introduced this ill-formed line into MAINTAINERS.
> >
> > Rectify it now.
> 
> There is a patch waiting for upstream:
> https://lore.kernel.org/linux-media/20200128145828.74161-1-andriy.shevchenko@linux.intel.com/
> 

Agree, either one of those two patches solves the issue.

Lukas

      reply	other threads:[~2020-02-01 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01 15:17 [PATCH] MAINTAINERS: correct entry in TI VPE/CAL DRIVERS section Lukas Bulwahn
2020-02-01 18:33 ` Andy Shevchenko
2020-02-01 19:20   ` Lukas Bulwahn [this message]

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=alpine.DEB.2.21.2002012018480.6548@felia \
    --to=lukas.bulwahn@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=bparrot@ti.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=robh@kernel.org \
    /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).