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 4/6] arm64: dts: qcom: sm8250-hdk: Enable the PCIe ports
Date: Fri, 23 Oct 2026 07:43:51 +0000 [thread overview]
Message-ID: <sashiko-outbox-182433@kernel.org> (raw)
In-Reply-To: <20261023072832.2642647-4-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-developed-by sign-off and From email mismatch
--
commit 330aa236347071fbfcbc8b5b9c4e5d1913e72fce
Author: ShiTou Hong <redstone.dcity@gmail.com>
arm64: dts: qcom: sm8250-hdk: Enable the PCIe ports
This commit adds the 3V3 fixed regulator node for pcie2 and enables the pcie0
and pcie2 controllers and their PHYs on the sm8250-hdk board.
> arm64: dts: qcom: sm8250-hdk: Enable the PCIe ports
>
> The sm8250-hdk has 2 PCIe ports which are not enabled in the dts.
> The pcie0 is for the on-board ath11k WiFi/BT module;
> while the pcie2 is for the M.2 connector.
>
> Add the 3V3 regulator node for pcie2.
> Enable the 2 pcie controllers and phys.
>
> Co-developed-by: KancyJoe <kancy2333@outlook.com>
> Signed-off-by: ShiTou Hong <dc_redstone@outlook.com>
[Severity: Low]
Per Documentation/process/submitting-patches.rst, every Co-developed-by: tag
denotes authorship and must be immediately followed by a matching
Signed-off-by: tag from the associated co-author:
Since Co-developed-by: denotes authorship, every Co-developed-by: must be
immediately followed by a Signed-off-by: of the associated co-author.
Should this include a Signed-off-by: tag for KancyJoe <kancy2333@outlook.com>
immediately following the Co-developed-by: line?
Also, the commit Author email address (redstone.dcity@gmail.com) does not
match the email address in the submitter's Signed-off-by: line
(dc_redstone@outlook.com). Should the Author header and Signed-off-by: tag
use matching email addresses?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261023072832.2642647-1-dc_redstone@outlook.com?part=4
next prev parent reply other threads:[~2026-10-23 7:43 UTC|newest]
Thread overview: 13+ 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-26 10:33 ` Konrad Dybcio
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
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 [this message]
2026-10-23 7:28 ` [PATCH 5/6] arm64: dts: qcom: sm8250-hdk: Add support of QCA6390 ShiTou Hong
2026-10-26 10:54 ` Konrad Dybcio
2026-10-23 7:28 ` [PATCH 6/6] arm64: dts: qcom: sm8250-hdk: Add PM8150b LEDs ShiTou Hong
2026-10-26 10:32 ` [PATCH 1/6] arm64: dts: qcom: sm8250-hdk: Enable the sdhc_2 port Konrad Dybcio
-- strict thread matches above, loose matches on Subject: below --
2026-10-22 11:35 ShiTou Hong
2026-10-22 11:35 ` [PATCH 4/6] arm64: dts: qcom: sm8250-hdk: Enable the PCIe ports ShiTou Hong
2026-10-22 11:46 ` sashiko-bot
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-182433@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 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.