Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "ShiTou Hong" <redstone.dcity@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 3/6] arm64: dts: qcom: sm8250-hdk: Add FSA4480 USB-C protocol chip
Date: Fri, 23 Oct 2026 07:51:01 +0000	[thread overview]
Message-ID: <sashiko-outbox-182442@kernel.org> (raw)
In-Reply-To: <20261023072832.2642647-3-dc_redstone@outlook.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] arm64: dts: qcom: missing co-author sign-off and mismatched author email
--

commit 1a1ede276cc0d97ceb67bad5a51673b00f7ce0c3
Author: ShiTou Hong <redstone.dcity@gmail.com>

arm64: dts: qcom: sm8250-hdk: Add FSA4480 USB-C protocol chip

This commit adds the FSA4480 USB-C switch node and configures the PM8150B
type-c module, USB OTG role switch, and DisplayPort altmode in
arch/arm64/boot/dts/qcom/sm8250-hdk.dts.

>     arm64: dts: qcom: sm8250-hdk: Add FSA4480 USB-C protocol chip
>
>     The sm8250-hdk has a USB-C port supporting OTG and DP altmode.
>     This is implemented with the FSA4480 chip,
>     which hasn't been added in the dts file.
>
>     Change the USB controller mode to OTG.
>     Enable the i2c controller for the chip and the dp controller.
>     Configure the PM8150b type-c module and vbus regulator.
>
>     Co-developed-by: KancyJoe <kancy2333@outlook.com>
>     Signed-off-by: ShiTou Hong <dc_redstone@outlook.com>

[Severity: Low]
As documented in Documentation/process/submitting-patches.rst:

    Co-developed-by: denotes authorship, every Co-developed-by: must be immediately
    followed by a Signed-off-by: of the associated co-author.

Should the Co-developed-by tag for KancyJoe <kancy2333@outlook.com> be
immediately followed by a matching Signed-off-by tag from KancyJoe?

Also, the commit Author header uses redstone.dcity@gmail.com while the
Signed-off-by line uses dc_redstone@outlook.com. Should these two email
addresses match?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261023072832.2642647-1-dc_redstone@outlook.com?part=3

  reply	other threads:[~2026-10-23  7:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23  7:28 [PATCH 1/6] arm64: dts: qcom: sm8250-hdk: Enable the sdhc_2 port ShiTou Hong
2026-10-23  7:28 ` [PATCH 2/6] arm64: dts: qcom: sm8250-hdk: Add LT9611UXC HDMI bridge ShiTou Hong
2026-10-23  7:28 ` [PATCH 3/6] arm64: dts: qcom: sm8250-hdk: Add FSA4480 USB-C protocol chip ShiTou Hong
2026-10-23  7:51   ` sashiko-bot [this message]
2026-10-23  7:28 ` [PATCH 4/6] arm64: dts: qcom: sm8250-hdk: Enable the PCIe ports ShiTou Hong
2026-10-23  7:43   ` sashiko-bot
2026-10-23  7:28 ` [PATCH 5/6] arm64: dts: qcom: sm8250-hdk: Add support of QCA6390 ShiTou Hong
2026-10-23  7:28 ` [PATCH 6/6] arm64: dts: qcom: sm8250-hdk: Add PM8150b LEDs ShiTou Hong
  -- strict thread matches above, loose matches on Subject: below --
2026-10-22 11:35 [PATCH 1/6] arm64: dts: qcom: sm8250-hdk: Enable the sdhc_2 port ShiTou Hong
2026-10-22 11:35 ` [PATCH 3/6] arm64: dts: qcom: sm8250-hdk: Add FSA4480 USB-C protocol chip ShiTou Hong

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=sashiko-outbox-182442@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=redstone.dcity@gmail.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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