From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Kalle Valo <kvalo@adurom.com>, Amit Kucheria <amit.kucheria@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
MSM <linux-arm-msm@vger.kernel.org>,
Andy Gross <andy.gross@linaro.org>,
Bjorn Andersson <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: Tue, 18 Dec 2018 10:21:42 +0100 [thread overview]
Message-ID: <4be46ec9-4d0c-7380-021d-d03d0ab0c9df@free.fr> (raw)
In-Reply-To: <87r2ef701w.fsf@purkki.adurom.net>
On 18/12/2018 08:42, Kalle Valo wrote:
> 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.
>>
>> Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org>
>> ---
>> MAINTAINERS | 14 ++++----------
>> 1 file changed, 4 insertions(+), 10 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 3318f30903b2..c9376030f77a 100644
>> --- 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
>
> IMHO this is pretty fragile in the long term. For example only due to
> historical reasons qualcomm wireless drivers currently under ath
> directory but who knows if at some point we switch using qcom (or
> qualcomm) directory.
I am failing to follow your logic.
(IIUC, you are talking about drivers/net/wireless/ath/ath10k)
The fact that the "qcom" or "msm" nomenclature is not used for this driver now
just means that an explicit F entry is required. The fact that it could be renamed
in the future just means that the entry would need to be updated or folded into a
more generic matching pattern. What am I missing?
> Also the wireless drivers might easily have filenames containing
> strings like "msm" or "qcom" (which I assume would match with "N"
> rules above).
Any driver (not just wireless) might match "msm" or "qcom". These could be excluded
with an X directive (as the proposed patch does, in fact).
Regards.
next prev parent reply other threads:[~2018-12-18 9:22 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
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 [this message]
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=4be46ec9-4d0c-7380-021d-d03d0ab0c9df@free.fr \
--to=marc.w.gonzalez@free.fr \
--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=kvalo@adurom.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®