From: sashiko-bot@kernel.org
To: phucduc.bui@gmail.com
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/2] PCI: tegra194: use dev_err_probe() for PERST GPIO
Date: Wed, 07 Oct 2026 10:56:28 +0000 [thread overview]
Message-ID: <sashiko-outbox-162893@kernel.org> (raw)
In-Reply-To: <20261007104847.507776-1-phucduc.bui@gmail.com>
> From: bui duc phuc <phucduc.bui@gmail.com>
>
> Use dev_err_probe() when getting the PERST GPIO to simplify error
> handling and properly handle -EPROBE_DEFER.
>
> Signed-off-by: bui duc phuc <phucduc.bui@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261007104847.507776-1-phucduc.bui@gmail.com?part=1
next prev parent reply other threads:[~2026-10-07 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 10:48 [PATCH 1/2] PCI: tegra194: use dev_err_probe() for PERST GPIO phucduc.bui
2026-10-07 10:48 ` [PATCH 2/2] PCI: tegra194: propagate REFCLK select GPIO errors phucduc.bui
2026-10-07 10:58 ` sashiko-bot
2026-10-07 10:56 ` sashiko-bot [this message]
2026-10-07 20:46 ` [PATCH 1/2] PCI: tegra194: use dev_err_probe() for PERST GPIO Bjorn Helgaas
2026-10-08 11:08 ` Bui Duc Phuc
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-162893@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=phucduc.bui@gmail.com \
--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