From: Joe Perches <joe@perches.com>
To: Amit Kucheria <amit.kucheria@linaro.org>, linux-kernel@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, andy.gross@linaro.org,
marc.w.gonzalez@free.fr, bjorn.andersson@linaro.org,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v1 1/1] MAINTAINERS: update list of qcom drivers
Date: Mon, 17 Dec 2018 09:21:29 -0800 [thread overview]
Message-ID: <d45ce5f7612ef579a9bc687bab4339f27ee35660.camel@perches.com> (raw)
In-Reply-To: <ced6f6be01195e706ded5548897ff72503780146.1545063166.git.amit.kucheria@linaro.org>
On Mon, 2018-12-17 at 21:49 +0530, Amit Kucheria wrote:
> Several drivers didn't have a specific maintainer (other than the
> subsystem maintainer). Switch to using the 'qcom' and 'msm' regex
> patterns to capture all of them and add exceptions to the couple of
> drivers that contain 'msm' but are not related to qcom hardware.
>
> Thanks to Marc for the idea to use the N regex.
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -1929,20 +1929,14 @@ M: Andy Gross <andy.gross@linaro.org>
> M: David Brown <david.brown@linaro.org>
> L: linux-arm-msm@vger.kernel.org
> S: Maintained
> -F: Documentation/devicetree/bindings/soc/qcom/
> -F: arch/arm/boot/dts/qcom-*.dts
> -F: arch/arm/boot/dts/qcom-*.dtsi
> -F: arch/arm/mach-qcom/
> -F: arch/arm64/boot/dts/qcom/*
> +N: qcom
> +N: msm
It is generally better to use a comprehensive list of F: patterns
over N: patterns as N: patterns are not used as properly maintained
entries for files matched by the get_maintainer.pl script.
git history is used by default for the N: entries and that can
cause whitespace style commit authors to be cc'd on various changes
to matched files.
Also msm is a pretty common filename pattern and the X: exclusions
for various matching but not associated files might need to be added
to quite often.
From MAINTAINERS:
N: Files and directories with regex patterns.
N: [^a-z]tegra all files whose path contains the word tegra
One pattern per line. Multiple N: lines acceptable.
scripts/get_maintainer.pl has different behavior for files that
match F: pattern and matches of N: patterns. By default,
get_maintainer will not look at git log history when an F: pattern
match occurs. When an N: match occurs, git log history is used
to also notify the people that have git commit signatures.
next prev parent reply other threads:[~2018-12-17 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1545063166.git.amit.kucheria@linaro.org>
2018-12-17 16:19 ` Amit Kucheria
2018-12-17 16:29 ` Marc Gonzalez
2018-12-17 17:21 ` Joe Perches [this message]
2018-12-17 18:50 ` Amit Kucheria
2018-12-18 0:28 ` Joe Perches
2018-12-18 7:42 ` Kalle Valo
2018-12-18 9:21 ` Marc Gonzalez
2018-12-18 10:09 ` Kalle Valo
2018-12-18 10:01 ` Amit Kucheria
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=d45ce5f7612ef579a9bc687bab4339f27ee35660.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=amit.kucheria@linaro.org \
--cc=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.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
all inboxes | Powered by JetHome®