From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Karsten Keil <isdn@linux-pingi.de>, Arnd Bergmann <arnd@arndb.de>,
"isdn4linux@listserv.isdn4linux.de"
<isdn4linux@listserv.isdn4linux.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: correct entries for ISDN/mISDN section
Date: Sat, 1 Feb 2020 20:32:35 +0200 [thread overview]
Message-ID: <CAHp75VeWPQhjfMK9i-Bzbyoc=h71PhHShf17HTE0eRF=eURM5g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2002011541360.24739@felia>
On Sat, Feb 1, 2020 at 4:46 PM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
> On Sat, 1 Feb 2020, Andy Shevchenko wrote:
> > On Saturday, February 1, 2020, Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
> Interesting... I did not know about that script.
>
> On the current master and next-20200131, it reports:
>
> 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 16777.
>
> I will send a patch to the TI VPE/CAL DRIVERS maintainers to fix that as
> well.
There is a patch waiting:
https://lore.kernel.org/linux-media/20200128145828.74161-1-andriy.shevchenko@linux.intel.com/
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-02-01 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 12:43 [PATCH] MAINTAINERS: correct entries for ISDN/mISDN section Lukas Bulwahn
2020-02-01 13:13 ` Arnd Bergmann
[not found] ` <CAHp75Veb1fUkKyJ1_q=iXq=aFqtFrGoVMzoCk15CGaqmARUB+w@mail.gmail.com>
2020-02-01 14:46 ` Lukas Bulwahn
2020-02-01 18:32 ` Andy Shevchenko [this message]
2020-02-01 18:41 ` Joe Perches
2020-02-01 19:15 ` Lukas Bulwahn
2020-02-01 20:45 ` Joe Perches
2020-02-01 21:29 ` Lukas Bulwahn
2020-02-02 20:43 ` Jakub Kicinski
2020-02-03 10:13 ` Andy Shevchenko
2020-02-03 11:07 ` Joe Perches
2020-02-03 11:17 ` Andy Shevchenko
2020-02-04 5:08 ` Lukas Bulwahn
2020-02-04 5:35 ` Joe Perches
2020-02-03 17:35 ` Jakub Kicinski
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='CAHp75VeWPQhjfMK9i-Bzbyoc=h71PhHShf17HTE0eRF=eURM5g@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=netdev@vger.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 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.