From: Joe Perches <joe@perches.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Adrian Ratiu <adrian.ratiu@collabora.com>,
devicetree@vger.kernel.org,
dri-devel <dri-devel@lists.freedesktop.org>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Neil Armstrong <narmstrong@baylibre.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Collabora Kernel ML <kernel@collabora.com>
Subject: Re: [PATCH] get_maintainer: Add email addresses from .yaml files
Date: Sun, 26 Apr 2020 23:33:02 -0700 [thread overview]
Message-ID: <79ade7bc8ce57ef11f94011bad1842372c61fdd7.camel@perches.com> (raw)
In-Reply-To: <20200427055755.GA21898@ravnborg.org>
On Mon, 2020-04-27 at 07:57 +0200, Sam Ravnborg wrote:
> Hi Joe.
Hi Sam.
> On Sun, Apr 26, 2020 at 10:40:52PM -0700, Joe Perches wrote:
> > .yaml files can contain maintainer/author addresses and it seems
> > unlikely or unnecessary that individual MAINTAINER file section
> > entries for each .yaml file will be created.
> >
> > So dd the email addresses found in .yaml files to the default
> ^
> add
Andrew, can you add the a to this please?
> Signed-off-by: Joe Perches <joe@perches.com>
> Acked-by: Sam Ravnborg <sam@ravnborg.org>
> Tested-by: Sam Ravnborg <sam@ravnborg.org>
>
> The patch did not apply on top of -rc3, but it was trivial to fix.
> Tested and works like a charm.
> Thanks for doing this!
As most of my patches, it was done using -next
cheers, Joe
next prev parent reply other threads:[~2020-04-27 6:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 11:19 Rule for bridge yaml dt binding maintainers? Adrian Ratiu
2020-04-20 17:59 ` Sam Ravnborg
2020-04-22 20:02 ` Rob Herring
2020-04-22 23:43 ` Joe Perches
2020-04-23 5:22 ` Sam Ravnborg
2020-04-27 5:40 ` [PATCH] get_maintainer: Add email addresses from .yaml files Joe Perches
2020-04-27 5:57 ` Sam Ravnborg
2020-04-27 6:33 ` Joe Perches [this message]
2020-04-27 20:04 ` Andrew Morton
2020-04-27 20:26 ` Joe Perches
2020-04-27 20:32 ` 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=79ade7bc8ce57ef11f94011bad1842372c61fdd7.camel@perches.com \
--to=joe@perches.com \
--cc=a.hajda@samsung.com \
--cc=adrian.ratiu@collabora.com \
--cc=akpm@linux-foundation.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.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).