From: Leo Liang <ycliang@andestech.com>
To: Hal Feng <hal.feng@starfivetech.com>
Cc: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
Sumit Garg <sumit.garg@linaro.org>,
Fabio Estevam <festevam@gmail.com>,
Minda Chen <minda.chen@starfivetech.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH v2] pcie: starfive: Remove the redundant print of probe success
Date: Thu, 18 Sep 2025 20:06:31 +0800 [thread overview]
Message-ID: <aMv1xw3TCXZJKcHq@swlinux02> (raw)
In-Reply-To: <20250901082418.60834-1-hal.feng@starfivetech.com>
On Mon, Sep 01, 2025 at 04:24:18PM +0800, Hal Feng wrote:
> The dev_err() is used incorrectly and we don't need the driver
> to state probe success.
>
> Signed-off-by: Hal Feng <hal.feng@starfivetech.com>
> ---
> drivers/pci/pcie_starfive_jh7110.c | 2 --
> 1 file changed, 2 deletions(-)
Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>
prev parent reply other threads:[~2025-09-18 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 8:24 [PATCH v2] pcie: starfive: Remove the redundant print of probe success Hal Feng
2025-09-18 12:06 ` Leo Liang [this message]
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=aMv1xw3TCXZJKcHq@swlinux02 \
--to=ycliang@andestech.com \
--cc=festevam@gmail.com \
--cc=hal.feng@starfivetech.com \
--cc=minda.chen@starfivetech.com \
--cc=sjg@chromium.org \
--cc=sumit.garg@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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