From: Thomas Gleixner <tglx@kernel.org>
To: Ciprian Costea <ciprianmarian.costea@oss.nxp.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Haibo Chen <haibo.chen@nxp.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Shawn Guo <shawnguo@kernel.org>,
Lucas Stach <l.stach@pengutronix.de>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mmc@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, s32@nxp.com,
Christophe Lizzi <clizzi@redhat.com>,
Alberto Ruiz <aruizrui@redhat.com>,
Enric Balletbo <eballetb@redhat.com>,
Eric Chanudet <echanude@redhat.com>,
Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
Subject: Re: [PATCH v4 6/8] irqchip: add ARCH_S32 dependency to Kconfig
Date: Mon, 09 Mar 2026 10:27:50 +0100 [thread overview]
Message-ID: <87h5qps67d.ffs@tglx> (raw)
In-Reply-To: <20260306161555.9000-7-ciprianmarian.costea@oss.nxp.com>
On Fri, Mar 06 2026 at 17:15, Ciprian Costea wrote:
That subject line is useless. It says that it adds a random dependency
to Kconfig, which tells nothing. Subject lines have to be descriptive
and useful on their own w/o the need to decode them through the actual
change log.
Just fold this change into the previous patch which adds the ARCH_S32
support into the driver.
Thanks,
tglx
next prev parent reply other threads:[~2026-03-09 9:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 16:15 [PATCH v4 0/8] arm64: Add initial support for NXP S32N79 SoC Ciprian Costea
2026-03-06 16:15 ` [PATCH v4 1/8] dt-bindings: interrupt-controller: fsl,irqsteer: add S32N79 support Ciprian Costea
2026-03-07 10:57 ` Krzysztof Kozlowski
2026-03-06 16:15 ` [PATCH v4 2/8] dt-bindings: mmc: fsl-imx-esdhc: " Ciprian Costea
2026-03-07 10:58 ` Krzysztof Kozlowski
2026-03-06 16:15 ` [PATCH v4 3/8] dt-bindings: arm: fsl: Add NXP S32N79 SoC and RDB board Ciprian Costea
2026-03-07 10:58 ` Krzysztof Kozlowski
2026-03-06 16:15 ` [PATCH v4 4/8] mmc: sdhci-esdhc-imx: add NXP S32N79 support Ciprian Costea
2026-03-09 3:13 ` Bough Chen
2026-03-11 9:11 ` Adrian Hunter
2026-03-06 16:15 ` [PATCH v4 5/8] irqchip/imx-irqsteer: " Ciprian Costea
2026-03-09 9:23 ` Thomas Gleixner
2026-03-09 9:40 ` Ciprian Marian Costea
2026-03-06 16:15 ` [PATCH v4 6/8] irqchip: add ARCH_S32 dependency to Kconfig Ciprian Costea
2026-03-09 9:27 ` Thomas Gleixner [this message]
2026-03-09 9:43 ` Ciprian Marian Costea
2026-03-06 16:15 ` [PATCH v4 7/8] arm64: dts: freescale: Add NXP S32N79 SoC support Ciprian Costea
2026-03-06 16:15 ` [PATCH v4 8/8] arm64: dts: freescale: Add NXP S32N79-RDB board support Ciprian Costea
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=87h5qps67d.ffs@tglx \
--to=tglx@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=adrian.hunter@intel.com \
--cc=aruizrui@redhat.com \
--cc=ciprianmarian.costea@oss.nxp.com \
--cc=clizzi@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eballetb@redhat.com \
--cc=echanude@redhat.com \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s32@nxp.com \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.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