From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>, Shawn Guo <shawnguo@kernel.org>,
Gregor Herburger <gregor.herburger@ew.tq-group.com>
Cc: Leo Li <leoyang.li@nxp.com>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@ew.tq-group.com
Subject: Re: [PATCH v2 6/6] MAINTAINERS: add tqml device trees to TQ-Systems entry
Date: Mon, 25 Sep 2023 08:48:34 +0200 [thread overview]
Message-ID: <e1723311-1612-4bb4-98fc-d94215d8f898@linaro.org> (raw)
In-Reply-To: <c1ab31ae-97ec-4630-818d-06cd37ea3d86@app.fastmail.com>
On 25/09/2023 07:30, Arnd Bergmann wrote:
> On Mon, Sep 25, 2023, at 03:04, Shawn Guo wrote:
>> + Arnd
>>
>> On Tue, Aug 29, 2023 at 11:27:02AM +0200, Gregor Herburger wrote:
>>> Update file entries for TQ-Systems Layerscape modules.
>>>
>>> Signed-off-by: Gregor Herburger <gregor.herburger@ew.tq-group.com>
>>> ---
>>
>> I do not have a branch for this file, so you may want to send the
>> change to Arnd directly.
>
> The MAINTAINERS files can usually go into the same branch
> as arch/arm/mach-*/ and arch/arm64/Kconfig changes. If you have
> nothing for that, merging this one along with the corresponding
> arch/arm64/boot/dts changes is also fine.
>
> We used to have a separate branch just for the maintainer
> file updates a long time ago, but they rarely cause conflicts.
>
> Whichever way you end up doing it, please ensure that the person
> sending the pull request or patch addresses it to:soc@kernel.org
> cc:linux-arm-kernel@lists.infradead.org to make it end up in
> patchwork, otherwise I'm more likely to miss it or expect that
> I'll get it as part of the normal pull requests.
Plus, there is no really reason to split such trivial maintainer change
into separate commit.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-09-25 6:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 9:26 [PATCH v2 0/6] TQMLS10xxA support Gregor Herburger
2023-08-29 9:26 ` [PATCH v2 1/6] arm64: dts: ls1043a: remove second dspi node Gregor Herburger
2023-08-29 9:26 ` [PATCH v2 2/6] dt-bindings: arm: fsl: Add TQ-Systems LS1043A/LS1046A based boards Gregor Herburger
2023-08-29 9:26 ` [PATCH v2 3/6] arm64: dts: freescale: add initial device tree for TQMLS1043A/TQMLS1046A Gregor Herburger
2023-09-25 0:59 ` Shawn Guo
2023-08-29 9:27 ` [PATCH v2 4/6] dt-bindings: arm: fsl: Add TQ-Systems LS1088 based boards Gregor Herburger
2023-08-29 9:27 ` [PATCH v2 5/6] arm64: dts: freescale: add initial device tree for TQMLS1088A Gregor Herburger
2023-08-29 9:27 ` [PATCH v2 6/6] MAINTAINERS: add tqml device trees to TQ-Systems entry Gregor Herburger
2023-09-25 1:04 ` Shawn Guo
2023-09-25 5:30 ` Arnd Bergmann
2023-09-25 6:48 ` Krzysztof Kozlowski [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=e1723311-1612-4bb4-98fc-d94215d8f898@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregor.herburger@ew.tq-group.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=robh+dt@kernel.org \
--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).