From: "Michal Vokáč" <michal.vokac@ysoft.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 6/6] MAINTAINERS: Add Michal Vokáč as yapp4 boards maintainer
Date: Mon, 13 Feb 2023 10:50:49 +0100 [thread overview]
Message-ID: <04c606f8-97d2-5eeb-17cd-0337563f19b3@ysoft.com> (raw)
In-Reply-To: <c08a0b99-a024-62b3-da2f-d2952e9ae130@linaro.org>
On 13. 02. 23 10:18, Krzysztof Kozlowski wrote:
>>>
>>> I don't think we add per-board maintainers. Otherwise, I have 50 more
>>> entries to add...
>>
>> I have got drawn into it by the checkpatch.pl script saying:
>>
>> WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
>>
>> So I went through the MAINTAINERS file and its git log with .dts related
>> changes. I found some individual board entries and quite recent changes
>> adding new ones. Hence I decided this could be right.
>
> They are not right, but solution to that took some time:
> https://lore.kernel.org/all/829b122da52482707b783dc3d93d3ff0179cb0ca.camel@perches.com/
>
OK, thank you for pointing that out!
Michal
prev parent reply other threads:[~2023-02-13 9:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 15:48 [PATCH 0/6] Add support for new boards in the imx6dl-yapp4 family Michal Vokáč
2023-02-10 15:48 ` [PATCH 1/6] dt-bindings: arm: fsl: Fix copy-paste error in comment Michal Vokáč
2023-02-11 11:45 ` Krzysztof Kozlowski
2023-03-13 8:27 ` Shawn Guo
2023-02-10 15:48 ` [PATCH 2/6] ARM: dts: imx6dl-yapp4: Change LED channel names according to dt-binding Michal Vokáč
2023-03-13 8:28 ` Shawn Guo
2023-03-13 8:48 ` Krzysztof Kozlowski
2023-03-13 10:57 ` Michal Vokáč
2023-02-10 15:48 ` [PATCH 3/6] ARM: dts: imx6dl-yapp4: Use reset-gpios property name Michal Vokáč
2023-03-13 8:29 ` Shawn Guo
2023-02-10 15:48 ` [PATCH 4/6] dt-bindings: arm: fsl: Add Y Soft IOTA Phoenix, Lynx, Pegasus and Pegasus+ Michal Vokáč
2023-02-11 11:45 ` Krzysztof Kozlowski
2023-02-10 15:48 ` [PATCH 5/6] ARM: dts: imx6dl-yapp43: Add support for new HW revision of the IOTA board Michal Vokáč
2023-03-13 8:23 ` Shawn Guo
2023-03-13 16:42 ` Michal Vokáč
2023-03-14 0:42 ` Shawn Guo
2023-02-10 15:48 ` [PATCH 6/6] MAINTAINERS: Add Michal Vokáč as yapp4 boards maintainer Michal Vokáč
2023-02-11 11:46 ` Krzysztof Kozlowski
2023-02-13 9:08 ` Michal Vokáč
2023-02-13 9:18 ` Krzysztof Kozlowski
2023-02-13 9:50 ` Michal Vokáč [this message]
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=04c606f8-97d2-5eeb-17cd-0337563f19b3@ysoft.com \
--to=michal.vokac@ysoft.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).