From: Nishanth Menon <nm@ti.com>
To: Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: Josua Mayer <josua@solid-run.com>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"kristo@kernel.org" <kristo@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"w.egorov@phytec.de" <w.egorov@phytec.de>,
"matthias.schiffer@ew.tq-group.com"
<matthias.schiffer@ew.tq-group.com>,
"d.haller@phytec.de" <d.haller@phytec.de>,
"francesco.dolcini@toradex.com" <francesco.dolcini@toradex.com>,
"joao.goncalves@toradex.com" <joao.goncalves@toradex.com>,
"emanuele.ghidoli@toradex.com" <emanuele.ghidoli@toradex.com>,
"ernest.vanhoecke@toradex.com" <ernest.vanhoecke@toradex.com>,
"rogerq@kernel.org" <rogerq@kernel.org>,
"eballetb@redhat.com" <eballetb@redhat.com>,
"robertcnelson@gmail.com" <robertcnelson@gmail.com>,
"afd@ti.com" <afd@ti.com>, "u-kumar1@ti.com" <u-kumar1@ti.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"luis.parga@ti.com" <luis.parga@ti.com>,
"srk@ti.com" <srk@ti.com>
Subject: Re: [PATCH v2 01/13] arm64: dts: ti: k3-am642-hummingboard-t: fix USB clocking for compliance
Date: Thu, 7 May 2026 10:47:05 -0500 [thread overview]
Message-ID: <20260507154705.oisyadsyrrvv53qj@upriver> (raw)
In-Reply-To: <440c9069-b8dc-4dba-9dca-3a6c94bfd52e@ti.com>
On 12:09-20260507, Siddharth Vadapalli wrote:
> On 06/05/26 19:47, Josua Mayer wrote:
> > Am 06.05.26 um 16:09 schrieb Siddharth Vadapalli:
> > > According to section "6.5.3 Normative Spread Spectrum Clocking (SSC)" of
> > > the USB 3.2 Specification, SSC should be enabled by default. This protects
> > > against EMI violations. Hence, enable internal SSC for USB SuperSpeed.
> > >
> > > Fixes: e2b691804319 ("arm64: dts: ti: k3-am642-hummingboard-t: Convert overlay to board dts")
> > > Fixes: bbef42084cc1 ("arm64: dts: ti: hummingboard-t: add overlays for m.2 pci-e and usb-3")
> > > Cc: <stable@vger.kernel.org>
> > > Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
> > > Acked-by: Josua Mayer <josua@solid-run.com>
> >
> > Your (submitter) Signed-off should always be last.
>
> I see both patterns in git log (Acked-by before Signed-off-by and Acked-by
> after Signed-off-by) for arch/arm64/boot/dts. When posting the v2 patch, I
> looked at a commit with Acked-by following a Signed-off-by and followed the
> sequence.
Documentation/process/maintainer-tip.rst,
Documentation/process/submitting-patches.rst etc.. Signed-off-by is the
last in the chain - always the handling order is maintained.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
https://ti.com/opensource
next prev parent reply other threads:[~2026-05-07 15:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 14:09 [PATCH v2 00/13] TI: K3 DTS: fix USB Clocking for Compliance Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 01/13] arm64: dts: ti: k3-am642-hummingboard-t: fix USB clocking for compliance Siddharth Vadapalli
2026-05-06 14:17 ` Josua Mayer
2026-05-07 6:39 ` Siddharth Vadapalli
2026-05-07 15:47 ` Nishanth Menon [this message]
2026-05-06 14:09 ` [PATCH v2 02/13] arm64: dts: ti: k3-am642-phyboard-electra-rdk: " Siddharth Vadapalli
2026-05-07 8:25 ` Wadim Egorov
2026-05-07 8:45 ` Siddharth Vadapalli
2026-05-07 15:44 ` Nishanth Menon
2026-05-07 12:56 ` Wadim Egorov
2026-05-06 14:09 ` [PATCH v2 03/13] arm64: dts: ti: k3-am642-sk: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 04/13] arm64: dts: ti: k3-am642-tqma64xxl: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 05/13] arm64: dts: ti: k3-am68-phyboard-izar: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 06/13] arm64: dts: ti: k3-am68-sk-baseboard: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 07/13] arm64: dts: ti: k3-am69-aquila: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 08/13] arm64: dts: ti: k3-am69-sk: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 09/13] arm64: dts: ti: k3-j721e-beagleboneai64: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 10/13] arm64: dts: ti: k3-j721e-common-proc-board: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 11/13] arm64: dts: ti: k3-j721e-sk: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 12/13] arm64: dts: ti: k3-j722s-evm: " Siddharth Vadapalli
2026-05-06 14:09 ` [PATCH v2 13/13] arm64: dts: ti: k3-j784s4-j742s2-evm-common: " Siddharth Vadapalli
2026-05-06 17:07 ` [PATCH v2 00/13] TI: K3 DTS: fix USB Clocking for Compliance Robert Nelson
2026-05-07 6:44 ` Siddharth Vadapalli
2026-05-07 15:59 ` Nishanth Menon
2026-05-07 16:24 ` Nishanth Menon
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=20260507154705.oisyadsyrrvv53qj@upriver \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=d.haller@phytec.de \
--cc=devicetree@vger.kernel.org \
--cc=eballetb@redhat.com \
--cc=emanuele.ghidoli@toradex.com \
--cc=ernest.vanhoecke@toradex.com \
--cc=francesco.dolcini@toradex.com \
--cc=joao.goncalves@toradex.com \
--cc=josua@solid-run.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.parga@ti.com \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=robertcnelson@gmail.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.com \
--cc=stable@vger.kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/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