From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Rob Herring <robh+dt@kernel.org>, Conor Dooley <conor@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v1] MAINTAINERS: add Conor as a dt-bindings maintainer
Date: Fri, 5 May 2023 08:40:50 +0200 [thread overview]
Message-ID: <ccc65444-d477-1f78-9c5a-042441da7cd7@linaro.org> (raw)
In-Reply-To: <CAL_JsqLUj4b0fpV_6juoeQqBY83GezZNh-UTH9vmaFAyEVUzPw@mail.gmail.com>
On 05/05/2023 02:02, Rob Herring wrote:
> On Thu, May 4, 2023 at 4:59 PM Conor Dooley <conor@kernel.org> wrote:
>>
>> From: Conor Dooley <conor.dooley@microchip.com>
>>
>> Rob asked if I would be interested in helping with the dt-bindings
>> maintenance, and since I am a glutton for punishment I accepted.
>>
>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>> ---
>> MAINTAINERS | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 4e9370793300..687d7a3d2e85 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -15697,6 +15697,7 @@ K: of_overlay_remove
>> OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS
>> M: Rob Herring <robh+dt@kernel.org>
>> M: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
>> +M: Conor Dooley <conor+dt@kernel.org>
>
> Do you really want '+dt'? I've never really used it, and I think it
> suffers from the same issue as MAINTAINERS. It won't get used
> consistently.
>
It works mostly for me and still helps the filters.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-05-05 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 21:58 [PATCH v1] MAINTAINERS: add Conor as a dt-bindings maintainer Conor Dooley
2023-05-05 0:02 ` Rob Herring
2023-05-05 5:39 ` Conor Dooley
2023-05-05 6:40 ` Krzysztof Kozlowski [this message]
2023-05-05 6:41 ` Krzysztof Kozlowski
2023-05-05 12:45 ` Rob Herring
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=ccc65444-d477-1f78-9c5a-042441da7cd7@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=robh+dt@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).