From: Shawn Guo <shawnguo2@yeah.net>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Xu Yang <xu.yang_2@nxp.com>, Chester Lin <chester62515@gmail.com>,
Matthias Brugger <mbrugger@suse.com>,
Ghennadi Procopciuc <ghennadi.procopciuc@oss.nxp.com>,
NXP S32 Linux Team <s32@nxp.com>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: s32g3: Fix whitespace issue in device tree
Date: Thu, 21 Aug 2025 16:04:56 +0800 [thread overview]
Message-ID: <aKbTKJqoxwKKJsu_@dragon> (raw)
In-Reply-To: <e4c5fe15-87c8-42d5-b4d7-09e3d1f7e712@suswa.mountain>
On Fri, Jul 18, 2025 at 06:21:00PM +0300, Dan Carpenter wrote:
> On Fri, Jul 18, 2025 at 08:58:19AM +0200, Krzysztof Kozlowski wrote:
> > On 17/07/2025 00:46, Dan Carpenter wrote:
> > > Checkpatch points out that this should use spaces instead of tabs.
> > > "ERROR: code indent should use tabs where possible".
> > >
> > > Reported-by: Xu Yang <xu.yang_2@nxp.com>
> > > Closes: https://lore.kernel.org/all/u7glt7mn33lbdeskbr4ily6tjjifvffy64llwpi5b2rrhx5tnv@y2h2y3oz3xc4/
> > > Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> > > ---
> >
> > Patches were not merged, so this should be squashed there... or you
> > meant they went with Greg USB? Then no, that's dissapointing, you are
> > not supposed to send DTS patches to Greg's subsystem.
>
> I worry that I have accidentally stepped into politics...
>
> Yes, it went through Greg's tree.
I don't find two DTS patches in v6.17-rc1. I tried to pick them up, but
this one doesn't apply. So you may want to resend them.
> I'm just using get_maintainer.pl.
> Looking at it now, Greg and linux-usb weren't even on the Cc list for
> the DTS patches. There was probably some b4 magic which let him apply
> the whole series.
>
> How was this supposed to have worked?
The DTS changes should be sent separately from usb driver ones.
Shawn
next prev parent reply other threads:[~2025-08-21 8:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1752703107.git.dan.carpenter@linaro.org>
2025-07-16 22:46 ` [PATCH 1/3] usb: chipidea: imx: Add a missing blank line Dan Carpenter
2025-07-21 2:24 ` Peter Chen (CIX)
2025-07-16 22:46 ` [PATCH 2/3] arm64: dts: s32g3: Fix whitespace issue in device tree Dan Carpenter
2025-07-17 16:07 ` Matthias Brugger
2025-07-18 6:58 ` Krzysztof Kozlowski
2025-07-18 15:21 ` Dan Carpenter
2025-08-21 8:04 ` Shawn Guo [this message]
2025-08-21 8:41 ` Krzysztof Kozlowski
2025-07-16 22:46 ` [PATCH 3/3] arm64: dts: s32g2: Re-order usbmisc device tree section Dan Carpenter
2025-07-17 16:06 ` Matthias Brugger
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=aKbTKJqoxwKKJsu_@dragon \
--to=shawnguo2@yeah.net \
--cc=chester62515@gmail.com \
--cc=conor+dt@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=ghennadi.procopciuc@oss.nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s32@nxp.com \
--cc=shawnguo@kernel.org \
--cc=xu.yang_2@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.